diff options
| author | bors <bors@rust-lang.org> | 2019-09-09 14:55:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-09-09 14:55:33 +0000 |
| commit | 8af4e096054bc97866feb9ac34a3cc11310d9d41 (patch) | |
| tree | 674fa413c112c14b63c87fb23e787ab51410daf6 /src/test/incremental/thinlto | |
| parent | 144d940c2fc1055fd9e2bcbd0bd21bf5591a5381 (diff) | |
| parent | e7d8cf85117c680f3e6dccc87b210a85512b9850 (diff) | |
| download | rust-8af4e096054bc97866feb9ac34a3cc11310d9d41.tar.gz rust-8af4e096054bc97866feb9ac34a3cc11310d9d41.zip | |
Auto merge of #4458 - flip1995:block_in_if_ext_macro, r=phansch
Allow block_in_if_{stmt,expr} in external macro
I found this by running `cargo fix --clippy` on quite a big codebase.
You could refactor this assert to
```rust
let block_expr = _;
assert!(block_expr);
```
but,
1. it doesn't increase the readability IMO
2. That isn't possible in a `debug_assert!`
I'm not sure though, if we should allow this for macros in general or just for external macros.
changelog: Allow `block_in_if_{stmt,expr}` in external macros
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions
