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

document "/&" syntax #3886

Closed
erickt opened this issue Oct 29, 2012 · 2 comments
Closed

document "/&" syntax #3886

erickt opened this issue Oct 29, 2012 · 2 comments
Labels
A-lifetimes Area: Lifetimes / regions E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone

Comments

@erickt
Copy link
Contributor

erickt commented Oct 29, 2012

@graydon says that a type that is suffixed with /&r describes that this type holds a borrowed pointer from the region r. This needs mentioning in our documentation.

@bblum
Copy link
Contributor

bblum commented Oct 30, 2012

@nikomatsakis

@catamorphism
Copy link
Contributor

This is discussed in the borrowed pointer tutorial already -- see the section "Returning borrowed pointers" -- as well as in the "Pointer types" section of the reference manual ("Borrowed pointers are written &content, or in some cases &f/content for some lifetime-variable f...") If you have suggestions for improvements to the existing doc, feel free to comment or open a new issue :-)

RalfJung pushed a commit to RalfJung/rust that referenced this issue Sep 17, 2024
support pthread primitives on FreeBSD

Fixes rust-lang/miri#3571: makes out pthread implementation support FreeBSD.

FreeBSD sets PHTREAD_MUTEX_DEFAULT == PHTREAD_MUTEX_ERRORCK, so the logic for handling "default vs explicitly set mutex kind" had to be adjusted.

The rest is just some general cleanup of the pthread logic, and I realized that we can enable the std::sync tests on Solarish.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-lifetimes Area: Lifetimes / regions 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

3 participants