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

Sidebar links on the website are confusing beginners #3332

Closed
z0w0 opened this issue Sep 1, 2012 · 3 comments
Closed

Sidebar links on the website are confusing beginners #3332

z0w0 opened this issue Sep 1, 2012 · 3 comments
Assignees
Milestone

Comments

@z0w0
Copy link
Contributor

z0w0 commented Sep 1, 2012

The website's documentation links on the side keep confusing beginners (I've seen this popup a number of times on #rust). They click the tutorial link under documentation thinking it's the same documentation for their version, but instead it's for the latest git master and then they get confused as to why the example code is broken.

@brson
Copy link
Contributor

brson commented Sep 1, 2012

Let's fix this for 0.4. We can rearrange the documentation links to emphasize the current version.

@brson
Copy link
Contributor

brson commented Sep 1, 2012

I pushed some changes to rust-lang.org to try to improve the situation. Now we link to the current-release and if you want the bleeding edge you have to chase it down through the wiki.

@ghost ghost assigned brson Sep 4, 2012
@brson
Copy link
Contributor

brson commented Sep 7, 2012

I'm going to call this done. Let me know if there are further improvements I can make.

@brson brson closed this as completed Sep 7, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
RalfJung pushed a commit to RalfJung/rust that referenced this issue Mar 3, 2024
add mpsc memory leak to trophy case
jaisnan pushed a commit to jaisnan/rust-dev that referenced this issue Jul 29, 2024
… memory initialization is checked (rust-lang#3332)

This PR introduces layout checks for types to instrument mutable pointer
casts. If two types have incompatible padding (e.g. a padding byte in
one is a data byte in the other or vice-versa), an "unsupported check"
assertion is inserted. This overapproximates for soundness, since the
casts do not cause UB themselves, but an alternative solution involves
tracking every MIR place, which is costly.

Resolves rust-lang#3324

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.
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

No branches or pull requests

2 participants