diff options
| author | bors <bors@rust-lang.org> | 2018-07-02 03:18:49 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-07-02 03:18:49 +0000 |
| commit | 45935640f058405c95c96308f3acfd5ac1535698 (patch) | |
| tree | 4eb48a11a4f747fc76381873c70c36355468141b /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 5df43114bcb42d4fbe4c1950016e4713cd4e5da7 (diff) | |
| parent | 43a0a65fa2d812c0e48e6cc60a985a4bf47bff57 (diff) | |
| download | rust-45935640f058405c95c96308f3acfd5ac1535698.tar.gz rust-45935640f058405c95c96308f3acfd5ac1535698.zip | |
Auto merge of #51866 - zackmdavis:hir_making_each_day_of_the_year, r=petrochenkov
add modifier keyword spans to hir::Visibility; improve unreachable-pub, private-no-mangle lint suggestions #50455 pointed out that the unreachable-pub suggestion for brace-grouped `use`s was bogus; #50476 partially ameliorated this by marking the suggestion as `Applicability::MaybeIncorrect`, but this is the actual fix. Meanwhile, another application of having spans available in `hir::Visibility` is found in the private-no-mangle lints, where we can now issue a suggestion to use `pub` if the item has a more restricted visibility marker (this seems much less likely to come up in practice than not having any visibility keyword at all, but thoroughness is a virtue). While we're there, we can also add a helpful note if the item does have a `pub` (but triggered the lint presumably because enclosing modules were private).  r? @nrc cc @Manishearth
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
