mut restriction lowering#159125
Conversation
| mut(in crate::a::E) e2: i32, //~ ERROR expected module, found enum `crate::a::E` [E0577] | ||
| mut(crate) e3: i32, | ||
| mut(self) e4: i32, | ||
| mut(super) e5: i32, //~ ERROR too many leading `super` keywords within `crate` [E0433] |
There was a problem hiding this comment.
cc @estebank I'm not in love with this error message, but it is consistent with pub(super) at the top level. The inline diagnostic is better and would probably be best served at the top level (modulo specific wording). What do you think?
(@CoCo-Japan-pan don't worry about handling this)
This comment has been minimized.
This comment has been minimized.
|
Changes to the size of AST and/or HIR nodes. cc @nnethercote |
a6284a4 to
c941bde
Compare
c941bde to
c060b6d
Compare
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
`mut` restriction lowering
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (f5dbb65): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -0.5%, secondary 0.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -1.9%, secondary 0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 488.317s -> 489.984s (0.34%) |
|
@bors r=jhpratt,Urgau rollup=iffy perf |
Rollup of 3 pull requests Successful merges: - #159125 (`mut` restriction lowering) - #159154 (compiler: redescribe llvmlike_vector_align as rust_vector_align) - #159157 (Better comment the struct used by `{read,write}_unaligned`) Failed merges: - #158732 (Apply MCP 1003 and move diagnostics.rs into its own module)
Rollup merge of #159125 - CoCo-Japan-pan:mut-restriction-lowering, r=jhpratt,Urgau `mut` restriction lowering This PR is part of the ongoing work to implement `mut` restrictions proposed in [RFC 3323](https://rust-lang.github.io/rfcs/3323-restrictions.html), and linked to a [GSoC proposal](https://rust-lang.zulipchat.com/#narrow/channel/421156-gsoc/topic/Project.3A.20Implementing.20impl.20and.20mut.20restrictions/with/592352432). It implements path resolution for `mut` restrictions and lowers the resolved information to HIR. Tracking issue: #105077 r? @Urgau cc @jhpratt
This PR is part of the ongoing work to implement
mutrestrictions proposed in RFC 3323, and linked to a GSoC proposal.It implements path resolution for
mutrestrictions and lowers the resolved information to HIR.Tracking issue: #105077
r? @Urgau
cc @jhpratt