-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make parser more robust against changes in the output of rustc
#11
Comments
FWIW this caused this change in rustc output to bounce in the past |
alexcrichton
added a commit
to alexcrichton/rust-crc32fast
that referenced
this issue
Dec 1, 2018
Unfortunately this has upstream bugs like djc/rustc-version-rs#11 which make the output non-robust in the face of changing rustc's output, so switch to a more flexible manual implementation.
srijs
pushed a commit
to srijs/rust-crc32fast
that referenced
this issue
Dec 1, 2018
Unfortunately this has upstream bugs like djc/rustc-version-rs#11 which make the output non-robust in the face of changing rustc's output, so switch to a more flexible manual implementation.
alexcrichton
added a commit
to alexcrichton/rand
that referenced
this issue
Dec 11, 2018
The `rustc_version` dependency is weighty and suffers from djc/rustc-version-rs#11 which makes it more difficult to change rustc over time.
alexcrichton
added a commit
to alexcrichton/rand
that referenced
this issue
Dec 13, 2018
The `rustc_version` dependency is weighty and suffers from djc/rustc-version-rs#11 which makes it more difficult to change rustc over time.
djc
added a commit
that referenced
this issue
Jan 11, 2021
djc
added a commit
that referenced
this issue
Jan 11, 2021
djc
added a commit
that referenced
this issue
Jan 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the parser of
rustc
s version information is relatively strict, expecting a clearly defined format of lines.However, seeing how
rustc
is unlikely to break its output in a backwards-incompatible way, but might add additional fields (as has already happened in the past), it might be more forward-compatible to just look for the"<key>: <value>"
lines this crate knows about and silently ignore the rest.The text was updated successfully, but these errors were encountered: