Skip to content

Detect traits being used as structs in check_expr_with_unifier#16867

Merged
bors merged 2 commits intorust-lang:masterfrom
wickerwaka:ice-16750
Sep 1, 2014
Merged

Detect traits being used as structs in check_expr_with_unifier#16867
bors merged 2 commits intorust-lang:masterfrom
wickerwaka:ice-16750

Conversation

@wickerwaka
Copy link

Not sure if this is addressing the root cause or just patching up a symptom. Also not sure if I should be adding a diagnostic code for this.

Fixes #16750
Fixes #15812

@alexcrichton
Copy link
Member

Could you add a test for this as well?

@alexcrichton
Copy link
Member

And yes adding an error code is fine, thanks!

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe this could be "use of trait {} as a struct constructor"

@huonw
Copy link
Contributor

huonw commented Aug 30, 2014

(docs about these sort of tests, it should be in src/test/compile-fail.)

Changed error to 'use of trait `{}` as a struct constructor'
bors added a commit that referenced this pull request Sep 1, 2014
Not sure if this is addressing the root cause or just patching up a symptom. Also not sure if I should be adding a diagnostic code for this.

Fixes #16750
Fixes #15812
@bors bors closed this Sep 1, 2014
@bors bors merged commit d3d14d6 into rust-lang:master Sep 1, 2014
lnicola pushed a commit to lnicola/rust that referenced this pull request Apr 7, 2024
update: add editor/extension information to bug report template

When attempting to reproduce issues, I encounter difficulties due to differences in versions of LSP clients and editors (such as rust-lang#16985, rust-lang#16867, and more)

This sometimes consumes a lot of efforts from contributors to communicate the details about LSP client information. Therefore, I believe adding editor/extension information to the issue template would be helpful for problem reproduction.
lnicola pushed a commit to lnicola/rust that referenced this pull request Apr 20, 2024
update: add editor/extension information to bug report template

When attempting to reproduce issues, I encounter difficulties due to differences in versions of LSP clients and editors (such as rust-lang#16985, rust-lang#16867, and more)

This sometimes consumes a lot of efforts from contributors to communicate the details about LSP client information. Therefore, I believe adding editor/extension information to the issue template would be helpful for problem reproduction.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ICE On Simple Example ICE when using a trait in a struct constructor

4 participants