We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
filter and distinct always return an array, regardless of input:
filter
distinct
repl:3:> (distinct @[1 2 3 0 -4 2 3]) @[1 2 3 0 -4] repl:4:> (filter pos? [1 2 3 0 -4 2 3]) @[1 2 3 2 3] repl:10:> (distinct "bookkeeper") @[98 111 107 101 112 114]
whereas drop-while and drop-until return either a tuple or string
drop-while
drop-until
repl:2:> (drop-until |(< $ 65) "foo123bar") "123bar" repl:3:> (drop-while pos? @[1 2 3 0 -4 2 3]) (0 -4 2 3)
seems like drop-while and drop-until should at least return an array when given an array.
The text was updated successfully, but these errors were encountered:
For reference, it looks like the drop-* siblings used to return arrays and that changed here.
drop-*
Found some PRs that might give some hints about the current state of things:
Sorry, something went wrong.
No branches or pull requests
filter
anddistinct
always return an array, regardless of input:whereas
drop-while
anddrop-until
return either a tuple or stringseems like
drop-while
anddrop-until
should at least return an array when given an array.The text was updated successfully, but these errors were encountered: