-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Questionable advice in bug report instructions #17848
Comments
I think the intent was indeed to get the version output. I think the phrasing is only odd in that it does not make that intent clear. (It is possible I am wrong about the intent here.) But there is an additional problem: Sometime between 0.10 and 0.11, we revised the We could fix both of these problems by revising the instructions to say something like:
|
Closing since #18217 was merged. |
…r=Veykril chore(config): remove `invocationLocation` in favor of `invocationStrategy` These flags were added to help rust-analyzer integrate with repos requiring non-Cargo invocations. The consensus is that having two independent settings are no longer needed. This change removes `invocationLocation` in favor of `invocationStrategy` and changes the internal representation of `InvocationStrategy::Once` to hold the workspace root. Closes rust-lang#17848.
Noticed in #17824.
This is either a really odd way to ask for the version, or a bit of advice that's no longer relevant. What should we say instead?
RUST_LOG=rustc rustc
is a bit too verbose — I killed it after it wrote 8.1 GB of logs compilingfn main() { let x = 3u; }
.The text was updated successfully, but these errors were encountered: