-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tait must be constrained if in sig #113169
Tait must be constrained if in sig #113169
Conversation
|
@@ -1,5 +1,4 @@ | |||
#![feature(type_alias_impl_trait)] | |||
// check-pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only test for which there was no workaround after this change.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #113370) made this pull request unmergeable. Please resolve the merge conflicts. |
b6612f4
to
62d2ddd
Compare
This comment has been minimized.
This comment has been minimized.
62d2ddd
to
64f3f5b
Compare
// check-pass | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR "reopens" #61863
the test doesn't really add too much new test coverage compared with other tests we already have.
☔ The latest upstream changes (presumably #117076) made this pull request unmergeable. Please resolve the merge conflicts. |
64f3f5b
to
fd06ad3
Compare
This comment has been minimized.
This comment has been minimized.
fd06ad3
to
d9b265f
Compare
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #117172) made this pull request unmergeable. Please resolve the merge conflicts. |
f0a4804
to
1d5ea10
Compare
Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 |
@rustbot ready |
…ped in a `fn main() {}` body
a54797c
to
85f2eca
Compare
@bors r=lcnr |
☀️ Test successful - checks-actions |
Finished benchmarking commit (02c7a59): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)Results (primary 0.5%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResults (primary 0.0%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 675.824s -> 676.122s (0.04%) |
Probably noise + we need the fix => @rustbot label: +perf-regression-triaged |
…r-errors Test that opaque types can't have themselves as a hidden type with incompatible lifetimes fixes rust-lang#122876 This PR used to add extra logic to prevent those cases, but after rust-lang#113169 this is implicitly rejected, because such usages are not defining.
…r-errors Test that opaque types can't have themselves as a hidden type with incompatible lifetimes fixes rust-lang#122876 This PR used to add extra logic to prevent those cases, but after rust-lang#113169 this is implicitly rejected, because such usages are not defining.
…r-errors Test that opaque types can't have themselves as a hidden type with incompatible lifetimes fixes rust-lang#122876 This PR used to add extra logic to prevent those cases, but after rust-lang#113169 this is implicitly rejected, because such usages are not defining.
…r-errors Test that opaque types can't have themselves as a hidden type with incompatible lifetimes fixes rust-lang#122876 This PR used to add extra logic to prevent those cases, but after rust-lang#113169 this is implicitly rejected, because such usages are not defining.
…r-errors Test that opaque types can't have themselves as a hidden type with incompatible lifetimes fixes rust-lang#122876 This PR used to add extra logic to prevent those cases, but after rust-lang#113169 this is implicitly rejected, because such usages are not defining.
Rollup merge of rust-lang#123782 - oli-obk:equal_tait_args, r=compiler-errors Test that opaque types can't have themselves as a hidden type with incompatible lifetimes fixes rust-lang#122876 This PR used to add extra logic to prevent those cases, but after rust-lang#113169 this is implicitly rejected, because such usages are not defining.
rust-lang/rust#113169 Signed-off-by: xxchan <xxchan22f@gmail.com>
r? @compiler-errors
kind of reverts #62423, but that PR only removed cycles in cases that we want to forbid now anyway.
see https://rust-lang.zulipchat.com/#narrow/stream/315482-t-compiler.2Fetc.2Fopaque-types/topic/lcnr.20oli.20meeting/near/370712246 for related discussion and motivating example
a TAIT showing up in a signature doesn't just mean it can register a hidden type, but that it must.
This is the design the types team decided upon for the following reasons
fixes #117861
reverts #125362 cc @Nilstrieb @joboet