Skip to content

No way to unwind without printing message #13736

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.

Sign up for GitHub

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

Jump to bottom
Closed
emberian opened this issue Apr 25, 2014 · 2 comments
Closed

No way to unwind without printing message #13736

emberian opened this issue Apr 25, 2014 · 2 comments

Comments

@emberian
Copy link
Member

cc @xales
@emberian
Copy link
Member Author

@alexcrichton do you see any reason that this isn't allowed?

@alexcrichton
Copy link
Member

You can use set_stderr with NullWriter to suppress task failure messages.

(closing because this is possible)

flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 28, 2024
@Jarcho
[bad_bit_mask] Fix FP on proc macros (rust-lang#13736)
b4163f0 
`clap-3.1.6` was not compiling on the rustc-perf benchmarks because of
this lint. Also, the user could not allow the lint on the macro itself
because it was checking Exprs, not whatever the input of `bitflags!` is.

```
error: &-masking with zero
   --> src/build/arg_settings.rs:197:1
    |
            (#[allow] here)
197 | / bitflags! {
198 | |     struct Flags: u32 {
199 | |         const REQUIRED         ...
200 | |         const MULTIPLE_OCC     ...
...   |
226 | |     }
227 | | }
    | |_^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#bad_bit_mask
    = note: this error originates in the macro `__impl_bitflags` which comes from the expansion of the macro `bitflags` (in Nightly builds, run with -Z macro-backtrace for more info)
```

changelog:  [`bad_bit_mask`]: Fix FP on procedural macros
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexcrichton @emberian