-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Using enclosing function's type parameter in enum definition yields ICE instead of error #5997
Comments
This still happens on today's master. Nominating for production ready. |
To be clear: I think the expected behavior here is an error |
just a bug, removing milestone/nomination. |
Triage, we're still creating types that are apparently fictitious and crashing. |
This no longer ICE, it now outputs an error: Adding the type parameter to the enum succeeds. Flagging as needs test. |
…tem_push, r=ebroto Fix FP in `same_item_push` Don't emit a lint when the pushed item doesn't have Clone trait Fix rust-lang#5979 changelog: Fix FP in `same_item_push` not to emit a lint when the pushed item doesn't have Clone trait
Add changelog for 1.48 beta [Rendered](https://github.com/ebroto/rust-clippy/blob/changelog_1_48/CHANGELOG.md) I've not added the PRs fixing `same_item_push` because those were backported, namely: * [rust-lang#5908](rust-lang/rust-clippy#5908) * [rust-lang#5997](rust-lang/rust-clippy#5997) * [rust-lang#6016](rust-lang/rust-clippy#6016) The following PR was reverted, so I've ignored it too: * [rust-lang#5984](rust-lang/rust-clippy#5984) ~~Also, I took the liberty of adding a "Thanks" section, naming all the contributors to this release. I think they deserve visibility in the changelog. Please tell me if we want to add this or maybe it's redundant given we link to the PRs?~~ changelog: none r? `@flip1995`
⇒ error: internal compiler error: fictitious type ty_param({idx: 0, def_id: {crate: 0, node: 1}}) in sizing_type_of()
⇒ error: attempt to use a type argument out of scope
The text was updated successfully, but these errors were encountered: