Skip to content

Add long diagnostics for E0382 #27182

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 1 commit into from
Aug 8, 2015
Merged

Conversation

AlisdairO
Copy link
Contributor

As title :-)
Part of #24407.

r? @Manishearth

that at most one writer or multiple readers can access the data at any one time.

If you wish to learn more about ownership in Rust, start with the chapter in the
Book:
Copy link
Member

Choose a reason for hiding this comment

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

Since it's supposed to be full markdown, I'm wondering if we should create urls like markdown : [Book](https://doc.rust-lang.org/book/ownership.html).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not sure - on the one hand, it's markdown, on the other hand, I imagine it'll look pretty weird when we print the message via rustc?

Copy link
Member

Choose a reason for hiding this comment

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

I'm working on this issue to print it directly markdown formatted (it's been a while however, too much things to do...).

Copy link
Member

Choose a reason for hiding this comment

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

Links can't be formatted in terminal output, so we should only use footnote-style notation for them

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So, am I okay to leave this as-is, or should I change it to footnote style?

Copy link
Member

Choose a reason for hiding this comment

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

as is for now IMO

@bors
Copy link
Collaborator

bors commented Jul 24, 2015

☔ The latest upstream changes (presumably #27265) made this pull request unmergeable. Please resolve the merge conflicts.

@GuillaumeGomez
Copy link
Member

@AlisdairO: A little rebased is needed here for r+.

@AlisdairO
Copy link
Contributor Author

Before I rebase this one, just want to check that it's wanted/correct? Perfectly happy to keep working on it if needed, but I'm not sure where this PR is going right now.

@GuillaumeGomez
Copy link
Member

Seems good for me, you'll need someone else's opinion. :)

of `x` when we set `y`. This is fundamental to Rust's ownership system: outside
of workarounds like `Rc`, a value cannot be owned by more than one variable.

The easiest way to address this problem is to implement `Copy` and `Clone` on
Copy link
Member

Choose a reason for hiding this comment

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

"if the type is your own"

@Manishearth
Copy link
Member

Yes, we want this, thanks for the effort 😄

(just needs rebase and one optional nit and should be good to go)

@AlisdairO
Copy link
Contributor Author

Fab, thanks a lot :). Rebased.

@Manishearth
Copy link
Member

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented Aug 8, 2015

📌 Commit dadc717 has been approved by Manishearth

@bors
Copy link
Collaborator

bors commented Aug 8, 2015

⌛ Testing commit dadc717 with merge a5d33d8...

bors added a commit that referenced this pull request Aug 8, 2015
@bors bors merged commit dadc717 into rust-lang:master Aug 8, 2015
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.

4 participants