Skip to content

Forbid the Sized bound on unsized types #16811

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

Merged
merged 2 commits into from
Sep 3, 2014
Merged

Conversation

nrc
Copy link
Member

@nrc nrc commented Aug 28, 2014

closes #16800
r? @nikomatsakis - I'm not 100% sure this is the right approach, it is kind of ad-hoc. The trouble is we don't have any intrinsic notion of which types are sized and which are not, we only have the Sized bound, so I have nothing to validate the Sized bound against.

@nrc
Copy link
Member Author

nrc commented Aug 31, 2014

@nikomatsakis now with type contents - much nicer :-) r?

bors added a commit that referenced this pull request Sep 3, 2014
closes #16800 
r? @nikomatsakis - I'm not 100% sure this is the right approach, it is kind of ad-hoc. The trouble is we don't have any intrinsic notion of which types are sized and which are not, we only have the Sized bound, so I have nothing to validate the Sized bound against.
@bors bors closed this Sep 3, 2014
@bors bors merged commit cc598e6 into rust-lang:master Sep 3, 2014
bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 17, 2024
fix: Fix method resolution snapshotting receiver_ty too early

Accidental change in rust-lang/rust-analyzer#16749 presumably caused some type mismatches in webrender
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 when compiling code
3 participants