seq on non-iterables #109
brandonstubbs
started this conversation in
Ideas
Replies: 3 comments
-
I think that for primitives like numbers, we should throw an error. The contract is ideally:
Otherwise, |
Beta Was this translation helpful? Give feedback.
0 replies
-
We should have a much more descriptive message in this case 😄 |
Beta Was this translation helpful? Give feedback.
0 replies
-
I propose we start a Github Discussion in case we want to discuss and extract actionable information from that into issues, so those are clear units of work that can be started and finished with a clear scope. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Opening this to discuss how we want to handle
seq
with non-iterables.At the moment when running a function that uses
seq
, map, first, first, etc. with a non-iterable, we get the following error:Do we want to throw a controlled error out of
seq
as clojurescript doesOr do we want to make the fix and let it fall back to
Object.entries
in theseq
function# ./node_cli.js -e '(println (first 1))' undefined
Beta Was this translation helpful? Give feedback.
All reactions