-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
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
Error message should be more informative when integer literal is being used as both integer and float #2317
Comments
Thanks for reporting this! To set expectations:
Finally, please be patient with the core team. They are trying their best with limited resources. |
What is the root cause, according to you? |
I'd say from a user standpoint, the root cause is that a thing which is slightly ambiguous/flexible by design (integer literal) is attempting to be subsequently used as two different types. Hitting this error message and using it for debugging is IMHO significantly more difficult than the usual incredibly helpful Elm debugging experience. For example, when I hit this in my project, I then looked at the place the variable was initialized and saw it was (the equivalent of) I think the difficult part is that this requires examination of 3 code locations (the variable initialization and the two or more locations where it is used), which may not be particularly close to one another, and may not be immediately obvious. I feel one of the strengths of Elm is precisely the lack of spooky-action-at-a-distance like this. |
Quick Summary: The error message when an integer literal is being used as both integer and float doesn't point out the root cause.
SSCCE
Source
Expected output
Error message explaining that the literal is being simultaneously used as both an
int
and afloat
.Received output
Additional Details
The text was updated successfully, but these errors were encountered: