-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rustc -g file.rs
does not work
#12811
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
Comments
There's already some discussion about this problem on reddit. |
bors
added a commit
that referenced
this issue
Mar 12, 2014
…xcrichton Fixes #12811 as described in the issue.
fasterthanlime
pushed a commit
to fasterthanlime/rust
that referenced
this issue
Jul 22, 2022
fix: Insert `pub(crate)` after doc comments and attribute macros Fixes rust-lang#12790 Original behavior was to insert `pub(crate)` at the `first_child_or_token`, which for an item with a comment or attribute macro, would put the visibility marker before the comment or macro, instead of after. This merge request alters the call to find the node with appropriate `SyntaxKind` in the `children_or_tokens`. It also adds a test case to the module to verify the behavior. Test case verifies function, module, records, enum, impl, trait, and type cases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After PR #12714, the
-g
option torustc
stopped working robustly.Basically, it seems to gobble up any succeeding token as the numeric argument setting the debuginfo level, so you cannot pass
-g
immediately before the input file name.Here is an example of the breakage:
My recommended fix: split the options so that
--debuginfo
requires the level parameter, while-g
does not accept a level parameter (and instead always has the same effect as--debuginfo 2
).The text was updated successfully, but these errors were encountered: