Skip to content

Conversation

mneumann
Copy link
Contributor

@mneumann mneumann commented Jan 6, 2015

Both FreeBSD and DragonFly define pthread_key_t as int, while Linux
defines it as uint. As pthread_key_t is used as an opaque type and
storage size of both int and uint are the same, this is rather a
cosmetic change.

Both FreeBSD and DragonFly define pthread_key_t as int, while Linux
defines it as uint. As pthread_key_t is used as an opaque type and
storage size of both int and uint are the same, this is rather a
cosmetic change.
@rust-highfive
Copy link
Contributor

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@vhbit
Copy link
Contributor

vhbit commented Jan 6, 2015

@mneumann considering this commit will conflict with #20634 I think it will be better merge them. Would you like to merge by yourself or prefer me to do that?

@mneumann
Copy link
Contributor Author

mneumann commented Jan 6, 2015

@vhbit merge if you like :)

@vhbit vhbit mentioned this pull request Jan 6, 2015
@alexcrichton
Copy link
Member

Closing for #20652

alexcrichton added a commit to alexcrichton/rust that referenced this pull request Jan 7, 2015
This is a manual merge of rust-lang#20627 and rust-lang#20634 to avoid conflicts in rollup and also avoid one roundtrip. I've leave copyright to original author.  If this one is moved to rollup original PR could be closed. cc @mneumann

@alexcrichton r?

Both FreeBSD and DragonFly define pthread_key_t as int, while Linux
defines it as uint. As pthread_key_t is used as an opaque type and
storage size of both int and uint are the same, this is rather a
cosmetic change.

iOS uses ulong (as OS X) so difference is critical on 64bit platforms.
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.

5 participants