Closed alygin closed 8 years ago
regular parsing looks good. I'm slightly confused about json, things like mismatched type
don't actually show the expected/found part, even though it's definitely in the json. Is that a new issue or was that there before?
@oli-obk, I left JSON parsing intact, just moved the loop on output lines one method higher. So, if there where some issues before, they are still there and it's unlikely that I introduced new ones. But I'll have a look at the problem you described since I'm fixing things there anyway.
I've made a trivial fix in json parsing, the message you expected is displayed now. But it seems that the json structure has changed since the parser was written and now they're out of sync. I think we need a separate issue for that because some preliminary research must be done to do the work correctly.
Links are also added to submessages and a minor code refactoring performed. Please, check it out.
The notion of transwarp beaming is like trying to hit a bullet with a smaller bullet whilst wearing a blindfold, riding a horse.
Since the json flag has a nice warning message, let's ignore whatever happens there xD
This looks good to me. Do you have anything additional or are we good to merge?
Absolutely ) I've done with what I was aiming and think we could merge if there're no objections.
I've improved parsing of output:
trace
. They can also exist as standalone messages.trace
).So, all the compiler and program messages are now neatly arranged, no information is lost in both standard and JSON modes. Works well with clippy.
Please, check, if everything is ok. Any feedback on the code, usability and anything else is highly appreciated.