Uh oh!
There was an error while loading. Please reload this page.
[WIP] Improve error reporting: Missing = on type declaration - #6603
[WIP] Improve error reporting: Missing = on type declaration#6603AndrewBoklashko wants to merge 1 commit into
Conversation
AndrewBoklashko
commented
Apr 24, 2019
@cartermp hi! |
cartermp
commented
Apr 24, 2019
@AndrewBoklashko What happens if you just use |
AndrewBoklashko
commented
Apr 24, 2019
@cartermp do you mean without |
cartermp
commented
Jun 27, 2020
@AndrewBoklashko Sorry for not getting back to you here. Are you still interested in pursuing this work? The codebase has diverged a lot, unfortunately. As for your question - I think there may have been something odd with the build on your machine. If you can try it against the latest master, that would give more a clue. |
cartermp
commented
Jul 4, 2020
Closing out old PR. @AndrewBoklashko please ping if you'd like this re-opened. |
This is my attempt to implement #1121.
I've been digging into FsLex/FsYacc parsing rules and was able to find out the changes I need to make.
But after I've made them, the project just doesn't build anymore. Without changes introduced in this PR build works fine for me so it's most likely that my code is wrong.
Unfortunately I don't get any error messages and I can't figure out where is the problem by myself.
I would like someone to take a look at this PR and advise me what is the problem here.
VS 2019 developer cmd output: