Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Related to #1102, this issue could act as an overall list for all the issues relating to error reporting from the compiler. I'll start the ball rolling by adding the ones mentioned in that issue plus a few more.
Up for grabs!
More discussion / on hold
If you have ideas for other error messages, please adhere to the following standard for new issues: -
@isaacabraham One error you might like to consider is a much better error message when a C# or C++ programmer uses
Now, as of F# 4.0, the use of explicit ref cells is far less common because implicit promotion of
But even without going that far, we could surely improve the error message for a misuse of
Can I leave it to you to add the specific issue for this?
I need help from @dsyme - I already contacted him
2016-08-15 18:46 GMT+02:00 Isaac Abraham email@example.com:
Just done a quick review here. There are a few issues that seem to me to be "up for grabs" i.e. there's been a discussion on the issue and there seems to be consensus on what the outcome should be - someone "just" needs to do the work.
There are also some that need some discussion to review them and decide the best way forward.
@enricosada Thanks hundred times for this link:
This is so true and especially to me as a newbie currently very challenging;
"In many cases, error messages cannot be interpreted without a sufficiently-precise model of the type
You have to study computer science with a special focus on ML, in order to get a drift about these type issues. I love F-Sharp really a ton and this is by far the most distracting thing to me yet, simply because I often lack any idea how this can be solved.
In truth, I think it starts even with the term "error messages". It should be not an error message only, it should contain an actual solution. Like Elm does that. And Reason and Rust. It seems to get quite standard. Which is, IMHO, overdue since decades.
I like to translate these solutions and I suggest a public announcement like in the form of a blog/twitter/slack post, which invites to the public contribution on this issue.
Thanks a lot ^-^