WIP Add lifted version of split#34
Conversation
|
I sorta think that if you go down this path, you ought to add lifted versions of many other string functions in the standard library: |
|
Oh, I definitely want to add all those lifted versions! The question is, what should they return when they encounter a |
|
Ah good point. Is there any common theme across base string functions that return scalars vs arrays? In the array case (i.e. ‘split’) where the correct return value for a non-null input is, say, an empty array, returning the same thing for a null input seems reasonable. For the scalar case maybe null propagation makes more sense? |
3 participants
This is probably a horrible idea and most likely I won't merge it. But hey, lets think about it a while. It is the only way that I can think of that would make the last query in queryverse/Query.jl#134 work out of the gate without a need to think about missing values... Maybe that goal is mistaken in the first place, though.
Essentially what this would do is treat a missing string passed to
splitas equivalent to an empty string...