Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions src/test/ui/lazy_normalization_consts/trait-resolution-breakage.rs
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
// check-pass

trait Trait<T> {
const ASSOC_CONST: usize = 0;
}

impl Trait<()> for u8 {}

// `u8::ASSOC_CONST` is resolved today, but will be ambiguous
// under lazy normalization.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It ought to be ambiguous today, I'd say...

Copy link
Contributor Author

@lcnr lcnr Jul 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, but it compiles on stable 😢 iirc you noted somewhere that this kind of local reasoning should get linted against/slowly phased out. Not completely sure where or when you mentioned that though

fn foo<T, U>() -> [(T, U); u8::ASSOC_CONST]
where
u8: Trait<T> + Trait<U>,
{
todo!()
}

fn main() {}
18 changes: 18 additions & 0 deletions src/test/ui/lazy_normalization_consts/unevaluated-consts.rs
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
// check-pass

// If we allow the parent generics here without using lazy normalization
// this results in a cycle error.
struct Foo<T, U>(T, U);

impl<T> From<[u8; 1 + 1]> for Foo<T, [u8; 1 + 1]> {
fn from(value: [u8; 1 + 1]) -> Foo<T, [u8; 1 + 1]> {
todo!();
}
}

fn break_me<T>()
where
[u8; 1 + 1]: From<[u8; 1 + 1]>
{}

fn main() {}