Skip to content

Compiler errors with associated_type_bounds #71443

Closed
@Plecra

Description

@Plecra

A couple minimal examples that cause the compiler to panic when using associated_type_bounds

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=b710f545c85c97f070bb6a907d265da1
https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=c4f697b2946691a3173aae09399dcc3c

I gotta run, so I can't go into further depth right now. These should probably be split into separate tracking issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: This is a bug.E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.F-associated_type_bounds`#![feature(associated_type_bounds)]`I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.glacierICE tracked in rust-lang/glacier.requires-nightlyThis issue requires a nightly compiler in some way.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions