The option -Z is now unstable #113

Closed
mkollaro opened this Issue Oct 10, 2016 · 9 comments

Comments

Projects
None yet
6 participants
@mkollaro

mkollaro commented Oct 10, 2016

I'm getting the following warning for all Rust files:
The option Z is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details.

I'm using rustc 1.12.0 (3191fbae9 2016-09-23) and rust.vim ref 2030019.

Syntastic version: 3.6.0                                                                                                                 
Info for filetype: rust                                                                                                                  
Global mode: active                                                                                                                      
Filetype rust is active                                                                                                                  
The current file will be checked automatically                                                                                           
Available checker: rustc                                                                                                                 
Currently enabled checker: rustc
@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Oct 10, 2016

Member

Hm,

let args = [relpath, '-Z', 'unstable-options', l:flag, a:pretty] + a:args
is the spot that it's used inside the extension. The file hasn't changed in a long time...

Member

steveklabnik commented Oct 10, 2016

Hm,

let args = [relpath, '-Z', 'unstable-options', l:flag, a:pretty] + a:args
is the spot that it's used inside the extension. The file hasn't changed in a long time...

@spinda

This comment has been minimized.

Show comment
Hide comment
@spinda

spinda Oct 11, 2016

Is there any way to silence this warning for the time being? It's quite annoying having the Syntastic window always open for .rs files.

spinda commented Oct 11, 2016

Is there any way to silence this warning for the time being? It's quite annoying having the Syntastic window always open for .rs files.

@Rolandde

This comment has been minimized.

Show comment
Hide comment
@Rolandde

Rolandde Oct 19, 2016

@spinda

 let g:syntastic_quiet_messages = {"regex": 'is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details'}

I'm not sure how this affects speed, but I doubt it will match any other errors.

@spinda

 let g:syntastic_quiet_messages = {"regex": 'is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details'}

I'm not sure how this affects speed, but I doubt it will match any other errors.

@spinda

This comment has been minimized.

Show comment
Hide comment
@spinda

spinda Oct 19, 2016

Thank you!

On Oct 19, 2016 12:14 PM, "Rolandde" notifications@github.com wrote:

@spinda https://github.com/spinda

let g:syntastic_quiet_messages = {"regex": 'is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details'}

I'm not sure how this affects speed, but I doubt it will match any other
errors.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#113 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHlwTWfHvdcfnkkMskzUNKsNsYQBrd1kks5q1mv2gaJpZM4KS3gk
.

spinda commented Oct 19, 2016

Thank you!

On Oct 19, 2016 12:14 PM, "Rolandde" notifications@github.com wrote:

@spinda https://github.com/spinda

let g:syntastic_quiet_messages = {"regex": 'is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details'}

I'm not sure how this affects speed, but I doubt it will match any other
errors.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#113 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHlwTWfHvdcfnkkMskzUNKsNsYQBrd1kks5q1mv2gaJpZM4KS3gk
.

ikouchiha47 added a commit to ikouchiha47/vim-rust-ide that referenced this issue Oct 28, 2016

ikouchiha47 added a commit to ikouchiha47/vim-rust-ide that referenced this issue Oct 28, 2016

@lpenz

This comment has been minimized.

Show comment
Hide comment
@lpenz

lpenz Nov 26, 2016

Contributor

I've tried adding

let g:syntastic_quiet_messages = {"regex": 'is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details'}

It does suppress the message, but I don't get any warnings from syntastic. I was only able to get syntastic working again by changing the plugin, initializing makeprg as follows:

let makeprg = self.makeprgBuild({})
Contributor

lpenz commented Nov 26, 2016

I've tried adding

let g:syntastic_quiet_messages = {"regex": 'is unstable and should only be used on the nightly compiler, but it is currently accepted for backwards compatibility; this will soon change, see issue #31847 for more details'}

It does suppress the message, but I don't get any warnings from syntastic. I was only able to get syntastic working again by changing the plugin, initializing makeprg as follows:

let makeprg = self.makeprgBuild({})
@BurntSushi

This comment has been minimized.

Show comment
Hide comment
@BurntSushi

BurntSushi May 14, 2017

Member

I just had the chance to update my rust-vim package and I'm now experiencing this change. I'm not really sure how the existing configuration is supposed to work at all in most projects, since it's effectively just calling rustc the_file.rs. For example, such a command always fails on the first extern crate it sees, since rustc isn't told where to find the crate.

In order to make the syntastic plugin useful to me again, I added this to my .vimrc, which restores the original behavior:

let g:syntastic_rust_rustc_args = '-Zparse-only'

I mostly develop on nightly Rust, so I don't have any good answers for folks using stable Rust...

Member

BurntSushi commented May 14, 2017

I just had the chance to update my rust-vim package and I'm now experiencing this change. I'm not really sure how the existing configuration is supposed to work at all in most projects, since it's effectively just calling rustc the_file.rs. For example, such a command always fails on the first extern crate it sees, since rustc isn't told where to find the crate.

In order to make the syntastic plugin useful to me again, I added this to my .vimrc, which restores the original behavior:

let g:syntastic_rust_rustc_args = '-Zparse-only'

I mostly develop on nightly Rust, so I don't have any good answers for folks using stable Rust...

@lpenz

This comment has been minimized.

Show comment
Hide comment
@lpenz

lpenz May 15, 2017

Contributor

The issue here is that -Zparse-only works only in nightly rust. So, adding it to the plugin will break stable.
Maybe add an option to the plugin that selects the rust channel? Or even detect it?

Contributor

lpenz commented May 15, 2017

The issue here is that -Zparse-only works only in nightly rust. So, adding it to the plugin will break stable.
Maybe add an option to the plugin that selects the rust channel? Or even detect it?

@BurntSushi

This comment has been minimized.

Show comment
Hide comment
@BurntSushi

BurntSushi May 15, 2017

Member

The issue here is that -Zparse-only works only in nightly rust.

Right. What I'm saying is that I don't understand how the current config works for anyone at any time. AFAIK, it will always fail if your code has any extern crate statements, no?

Member

BurntSushi commented May 15, 2017

The issue here is that -Zparse-only works only in nightly rust.

Right. What I'm saying is that I don't understand how the current config works for anyone at any time. AFAIK, it will always fail if your code has any extern crate statements, no?

@lpenz

This comment has been minimized.

Show comment
Hide comment
@lpenz

lpenz May 15, 2017

Contributor

I did a quick test here, and you are right.
I looked at what emacs' flycheck does, and it looks like it uses "-Z no-trans -Z unstable-options", which will also stop working, it seems. I'm not really sure where to go from here... Maybe the user can add -L for the paths of external crates?

Contributor

lpenz commented May 15, 2017

I did a quick test here, and you are right.
I looked at what emacs' flycheck does, and it looks like it uses "-Z no-trans -Z unstable-options", which will also stop working, it seems. I'm not really sure where to go from here... Maybe the user can add -L for the paths of external crates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment