You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you ask the mir-json tools for their version they print the rustc version, which is important, but realistically they should also print the mir-json version. Maybe also the current JSON schema version too, now that we have one.
In order to do this we need a version, but there is actually one in the cargo metadata (maybe we should bump it for the recent JSON changes?) so this shouldn't be that difficult to arrange.
The text was updated successfully, but these errors were encountered:
I agree that we should do this. I'm unclear if the rustc API offers a clean way to override the behavior of the --version flag, but if nothing else, we could reimplement --version ourselves. (The rustc implementation can be found here.)
Currently if you ask the mir-json tools for their version they print the rustc version, which is important, but realistically they should also print the mir-json version. Maybe also the current JSON schema version too, now that we have one.
In order to do this we need a version, but there is actually one in the cargo metadata (maybe we should bump it for the recent JSON changes?) so this shouldn't be that difficult to arrange.
The text was updated successfully, but these errors were encountered: