Fix feature gate for repr(simd)#158523
Conversation
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. Some changes occurred in compiler/rustc_attr_parsing |
e113cdf to
c5388d8
Compare
|
@rustbot ready |
|
Makes sense to me. Thanks for cleaning this up. @rfcbot fcp merge lang |
|
@traviscross has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns. |
|
@rfcbot reviewed |
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
|
@rfcbot reviewed |
|
Took a moment to realize that this is both no longer allowing Looks fine, though. |
|
I was pondering whether this is clearly a bug and thus we should just skip the 10-day wait since the branch is Friday(?). Mark pointed out that it's already on stable, though, so if it waits another release it's no big deal. |
We do currently allow the other repr variants on macro calls #[repr(C)]
println!();with the same "1.91 ..= beta give no diagnostic output" problem. I'm currently running crater on that (#158816), any breakage from this PR should also show up in it. |
The following code currently compiles on stable rust:
This has the following behavior:
This PR changes this to a feature gate error.
r? @mejrs