Add new unstable attribute: #[export_visibility = ...].#151431
Add new unstable attribute: #[export_visibility = ...].#151431anforowicz wants to merge 1 commit intorust-lang:mainfrom
#[export_visibility = ...].#151431Conversation
|
Some changes occurred in compiler/rustc_hir/src/attrs cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_passes/src/check_attr.rs cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_attr_parsing |
|
r? @chenyukang rustbot has assigned @chenyukang. Use |
|
i had a quick look, mostly looks good, but i'd like to maybe @JonathanBrouwer take a look on this as well, i may overlooked something r? JonathanBrouwer |
|
Would like to take a look, will do so tomorrow :) |
This comment has been minimized.
This comment has been minimized.
|
Reminder, once the PR becomes ready for a review, use |
2043b51 to
8dc8f60
Compare
This comment has been minimized.
This comment has been minimized.
8dc8f60 to
6ccbf57
Compare
88ddd87 to
a741ebc
Compare
a741ebc to
aa26225
Compare
This comment has been minimized.
This comment has been minimized.
8a51a4b to
6441282
Compare
This comment has been minimized.
This comment has been minimized.
|
I believe that should be reserved for approving reviews. Like No need for credit for drive by reviews, thank you for the thought though :) |
|
Ah, then only r=me :) |
This comment has been minimized.
This comment has been minimized.
|
Thanks for all the review feedback @JonathanBrouwer and @tgross35!
It seems fixed now - the automated checks for this PR are green. FWIW I am still having trouble testing this PR locally, but maybe this shouldn't block merging the PR. The trouble I am experiencing is that after rebasing I am getting (unrelated, also repro-able at |
71f2d9f to
7fa9d42
Compare
I started from scratch (
FWIW I have (blindly, without rebuilding/testing locally) rebased again and pushed the new commit. |
This comment has been minimized.
This comment has been minimized.
I hit the same issue earlier this week. The reason is the my system GCC got upgraded to a version that enables sframes by default, which lld does not support, causing these linker errors. I worked around it by building with |
|
@bors r+ rollup |
Thanks for chiming in. It's quite possible that we are experiencing the same issue. OTOH, when running |
|
Actually @bors rollup=iffy |
…nathanBrouwer Add new unstable attribute: `#[export_visibility = ...]`. This PR is an implementation of the RFC tracked in rust-lang#151425
Rollup of 15 pull requests Successful merges: - #151431 (Add new unstable attribute: `#[export_visibility = ...]`.) - #146900 (Add avr_target_feature) - #152033 (Rename trait `DepNodeParams` to `DepNodeKey`) - #152142 (Convert to inline diagnostics in `rustc_hir_typeck`) - #152020 (Remove dummy loads on offload codegen) - #152023 (Some `rustc_query_system` cleanups) - #152068 (Convert to inline diagnostics in `rustc_resolve`) - #152081 (Port depgraph testing attributes to parser) - #152090 (Port reexport_test_harness_main to attr parser) - #152105 (Convert to inline diagnostics in `rustc_ast_lowering`) - #152108 (Convert to inline diagnostics in `rustc_expand`) - #152114 (Convert to inline diagnostics in `rustc_mir_transform`) - #152115 (Convert to inline diagnostics in `rustc_metadata`) - #152116 (Remove rustdoc GUI flaky test) - #152128 (Adopt matches-logical-or-141497.rs to LLVM HEAD) Failed merges: - #152070 (Convert to inline diagnostics in `rustc_pattern_analysis`) - #152106 (Convert to inline diagnostics in `rustc_ast_passes`) - #152109 (Convert to inline diagnostics in `rustc_errors`) - #152117 (Convert to inline diagnostics in `rustc_trait_selection`) - #152118 (Convert to inline diagnostics in `rustc_codegen_ssa`) - #152119 (Convert to inline diagnostics in `rustc_middle`) - #152126 (Convert to inline diagnostics in `rustc_mir_build`) - #152131 (Port rustc_no_implicit_bounds attribute to parser.)
|
Failed in rollup in @bors r- |
This comment has been minimized.
This comment has been minimized.
a4aff4b to
9e65da3
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
The failure in the |
yes, all PR failed for this CI error. |
This PR is an implementation of the RFC tracked in #151425