Remove -Z no-trans support? #281
Comments
|
IMO there's no technical reason for using |
ehuss
added a commit
to ehuss/sublime-rust
that referenced
this issue
May 28, 2018
- Remove support for -Z no-trans on-save checking (fixes rust-lang#281). - Update some tests for latest nightly. - Pin nightly and clippy to a known-good version for Travis. This should ensure that minor issues don't cause unrelated PRs to fail. This also configures the beta/nightly jobs to allow failure. I have a cron job on my own repository set up so I will be notified whenever things break, and I'll send PRs when necessary.
jasonwilliams
pushed a commit
that referenced
this issue
Jun 5, 2018
- Remove support for -Z no-trans on-save checking (fixes #281). - Update some tests for latest nightly. - Pin nightly and clippy to a known-good version for Travis. This should ensure that minor issues don't cause unrelated PRs to fail. This also configures the beta/nightly jobs to allow failure. I have a cron job on my own repository set up so I will be notified whenever things break, and I'll send PRs when necessary.
jimenezrick
added a commit
to jimenezrick/ale
that referenced
this issue
Aug 10, 2018
The rust compiler renamed the option '-Z no-trans' to '-Z no-codegen'. rust-lang/rust-enhanced#281
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
-Z no-transoption will be soon renamed to-Z no-codegen(see rust-lang/rust#50615). There is still legacy support for the on-save checking to use this mode instead ofcargo check. I'd prefer just to remove support forno-trans, since I don't think there is a good reason to use it nowadays. Alternatively, we can check the rustc version and use the new flag if anyone actually still wants it.Rust Enhanced Version
v2.11.0
The text was updated successfully, but these errors were encountered: