Suppress MIR comments of FnDef and unit types#75670
Conversation
|
@bors r+ Nice! If you want to do something else along this line, we should really suppress the |
|
📌 Commit 0f7a43c861cb07aadcd5efdc328184ec9023a452 has been approved by |
|
@bors r- |
432fb42 to
7c4d315
Compare
src/test/mir-opt/const_prop/tuple_literal_propagation.main.ConstProp.diff
Show resolved
Hide resolved
|
r=me with CI passing |
|
CI is green. |
|
@bors r+ |
|
📌 Commit 7c4d315 has been approved by |
…-obk Suppress MIR comments for FnDef in ty::Const An expansion of rust-lang#75566. The comments in MIR constant already contains `ty::Contains` comments.
|
Failed in #75712 (comment), @bors r- |
|
However, profiler is disable by default: Line 220 in 5f6fcad So the test cannot be run in my machine. Does profiler need support from LLVM ? I am using local LLVM if that count. |
4cdef08 to
230b70e
Compare
230b70e to
bb34238
Compare
bb34238 to
86cf461
Compare
|
Done! |
|
@bors r+ p=1 (let's schedule it before other mir-opt PRs) |
|
📌 Commit 86cf461 has been approved by |
| _6 = _3; // scope 4 at $DIR/array-index-is-temporary.rs:16:25: 16:26 | ||
| _5 = const foo(move _6) -> bb1; // scope 4 at $DIR/array-index-is-temporary.rs:16:21: 16:27 | ||
| // ty::Const | ||
| // + ty: unsafe fn(*mut usize) -> u32 {foo} |
There was a problem hiding this comment.
The exact type of functions can sometimes be useful.
There was a problem hiding this comment.
The type is still shown right below (though we should probably cut out the val part of the literal field as it's useless for zsts.
|
☀️ Test successful - checks-actions, checks-azure |
Suppress "const" prefix of FnDef constants in MIR dump I [was asked][1] to suppress the `const` infront of `FnDef`. I tried to suppress comments for other types, but turned out that `const ()` and `()` is different: rust-lang#75697 (comment) [1]: rust-lang#75670 (comment)
An expansion of #75566.
Comments of FnDef MIR constant already contain
ty::Containscomments.