Improve value restriction error message #1103#15877
Conversation
0f861c4 to
5d71c81
Compare
|
Ready for review |
vzarytovskii
left a comment
There was a problem hiding this comment.
This lgtm, @dotnet/fsharp-team-msft
...ComponentTests/Conformance/BasicGrammarElements/ValueRestriction/E_NotMemberOrFunction01.fsx
Outdated
Show resolved
Hide resolved
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@Happypig375 looks like this somehow intertwined with the latest parens removal code fix. Would you like to look at it? I can jump on that in the upcoming days if you want to want to bother. Should be something simple though hopefully. |
|
Sorry false alarm, updating the branch. |
|
Please do not let this PR stale. the new error message is much better. |
|
Thanks for reminding, Edgar. @Happypig375 will you have a moment to resolve the conflicts and address the remaining notes? If not, I can help with that this week. |
|
I can revisit this next week but @psfinaki if you want you can go ahead with this PR |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@Happypig375 so I'll be merging this - thanks for the PR! |
Improve value restriction error message, relates to #1103, fixes #1161
Implemented message for value restriction error
For function values
For non-function values