Skip to content
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

message regarding owned bound is overly cryptic #3366

Closed
nikomatsakis opened this issue Sep 3, 2012 · 4 comments
Closed

message regarding owned bound is overly cryptic #3366

nikomatsakis opened this issue Sep 3, 2012 · 4 comments
Labels
A-typesystem Area: The type system C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@nikomatsakis
Copy link
Contributor

This example:

https://gist.github.com/3562945

gives a pretty cryptic message. It ought to name the type variable which requires the owned bound.

@nikomatsakis
Copy link
Contributor Author

Blocked on #2951.

@bstrie
Copy link
Contributor

bstrie commented May 6, 2013

Is there a more minimal test case for this?

@emberian
Copy link
Member

emberian commented Jul 7, 2013

@bstrie it'd be pretty hard to find a less minimal one

@huonw
Copy link
Member

huonw commented Aug 28, 2013

Triage: #2951 is now closed, and the following gives a sensible error message, so I'm going to close this (reopen if the testcase below is demonstrating something different to the 1 year old mega-example above).

fn needs_send<T: Send>(_: T) {}
fn no_send<SomeParamName>(x: SomeParamName) { needs_send(x) }
$ rustc --lib 3366.rs
3366.rs:2:46: 2:56 error: instantiating a type parameter with an incompatible type `SomeParamName`, which does not fulfill `Send`
3366.rs:2 fn no_send<SomeParamName>(x: SomeParamName) { needs_send(x) }
                                                        ^~~~~~~~~~
error: aborting due to previous error

@huonw huonw closed this as completed Aug 28, 2013
RalfJung pushed a commit to RalfJung/rust that referenced this issue Mar 9, 2024
compiletest: create fresh tempdir for tests to use

Fixes rust-lang/miri#3364
RalfJung pushed a commit to RalfJung/rust that referenced this issue Mar 9, 2024
compiletest: create fresh tempdir for tests to use

Fixes rust-lang/miri#3364
jaisnan pushed a commit to jaisnan/rust-dev that referenced this issue Jul 29, 2024
Update Rust toolchain from nightly-2024-07-19 to nightly-2024-07-20
without any other source changes.
This is an automatically generated pull request. If any of the CI checks
fail, manual intervention is required. In such a case, review the
changes at https://github.com/rust-lang/rust from
rust-lang@5affbb1
up to
rust-lang@9057c3f.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-typesystem Area: The type system C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

4 participants