Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upPeople are pointed to a non-existing repo #430
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Oct 28, 2015
Member
I think the whole message needs to be changed.
It was written at a time when I wasn't sure if there were bugs in the implementation of signals. If there were, you would hit this.
Nowadays, pretty much every report that mentions this is due to a problem somewhere not in the compiler or core. Maybe that is user code, maybe that is elm-reactor doing bad things.
So I think the best thing to do would be to reformulate the message to help people understand what went wrong in their stuff. We can pretend the elm-reactor stuff is fixed. Can you try to find all the issues (open or closed) on elm-compiler that came from this message? From there we can try to craft something more helpful.
|
I think the whole message needs to be changed. It was written at a time when I wasn't sure if there were bugs in the implementation of signals. If there were, you would hit this. Nowadays, pretty much every report that mentions this is due to a problem somewhere not in the compiler or core. Maybe that is user code, maybe that is elm-reactor doing bad things. So I think the best thing to do would be to reformulate the message to help people understand what went wrong in their stuff. We can pretend the elm-reactor stuff is fixed. Can you try to find all the issues (open or closed) on elm-compiler that came from this message? From there we can try to craft something more helpful. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Oct 28, 2015
Contributor
This seems to be the list of issues (open or closed) on elm-compiler that came from this message:
|
This seems to be the list of issues (open or closed) on elm-compiler that came from this message: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rtfeldman
Oct 30, 2015
Member
Exceptions thrown from subscription callbacks in JS ports are by far the most common culprit here in my experience, for what it's worth.
|
Exceptions thrown from subscription callbacks in JS ports are by far the most common culprit here in my experience, for what it's worth. |
jvoigtlaender commentedOct 27, 2015
What repo should https://github.com/elm-lang/core/blob/7ef42ccda13bb5f884330b9da0b283a95e1ec040/src/Native/Runtime.js#L59 be pointing to? Is it elm-reactor? Or core?