Skip to content

Rolling up PRs in the queue #14867

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 16 commits into from
Jun 13, 2014
Merged

Rolling up PRs in the queue #14867

merged 16 commits into from
Jun 13, 2014

Conversation

alexcrichton
Copy link
Member

No description provided.

pcwalton and others added 16 commits June 13, 2014 13:53
the leading quote part of the identifier for the purposes of hygiene.

This adopts @jbclements' solution to rust-lang#14539.

I'm not sure if this is a breaking change or not.

Closes rust-lang#12512.

[breaking-change]
RFC rust-lang#27.

After a snapshot, the old syntax will be removed.

This can break some code that looked like `foo as &Trait:Send`. Now you
will need to write `foo as (&Trait+Send)`.

Closes rust-lang#12778.

[breaking-change]
If the compiler is built with --{llvm,jemalloc,libuv}-root, then the configure
script can skip updating these submodules.

Closes rust-lang#14822
The docstring stated it was a intersection iterator, when in fact it is the union iterator
The `Any` docs previously did not state that only `'static` types implement it.
This commit fixes a bug in the calculation of the hash of a type which didn't
factor in the length of a constant-sized vector. As a result of this, a type
placed into an Any of a fixed length could be peeled out with any other fixed
length in a safe manner.
Once a native mutex has been used once, it is never allowed to be moved again.
This is because some pthreads implementations take pointers inside the mutex
itself.

This commit adds stern wording around the methods on native mutexes, and fixes
one use case in the codebase. The Mutex type in libsync was susceptible to
movement, so the inner static mutex is now boxed to ensure that the address of
the native mutex is constant.
Rust no longer has support for JIT compilation, so it doesn't currently
require a PaX MPROTECT exception. The extended attributes are preferred
over modifying the binaries so it's not actually going to work on most
systems like this anyway.

If JIT compilation ends up being supported again, it should handle this
by *always* applying the exception via an extended attribute without
performing auto-detection of PaX on the host. The `paxctl` tool is only
necessary with the older method involving modifying the ELF binary.
only known post-monomorphization, and report `transmute` errors before
the code is generated for that `transmute`.

This can break code that looked like:

    unsafe fn f<T>(x: T) {
        let y: int = transmute(x);
    }

Change such code to take a type parameter that has the same size as the
type being transmuted to.

Closes rust-lang#12898.

[breaking-change]
Closes rust-lang#14797 (librustc: Fix the issue with labels shadowing variable names by making)
Closes rust-lang#14823 (Improve error messages for io::fs)
Closes rust-lang#14827 (libsyntax: Allow `+` to separate trait bounds from objects.)
Closes rust-lang#14834 (configure: Don't sync unused submodules)
Closes rust-lang#14838 (Remove typo on collections::treemap::UnionItems)
Closes rust-lang#14839 (Fix the unused struct field lint for struct variants)
Closes rust-lang#14840 (Clarify `Any` docs)
Closes rust-lang#14846 (rustc: [T, ..N] and [T, ..N+1] are not the same)
Closes rust-lang#14847 (Audit usage of NativeMutex)
Closes rust-lang#14850 (remove unnecessary PaX detection)
Closes rust-lang#14856 (librustc: Take in account mutability when casting array to raw ptr.)
Closes rust-lang#14859 (librustc: Forbid `transmute` from being called on types whose size is)
Closes rust-lang#14860 (Fix `quote_pat!` & parse outer attributes in `quote_item!`)
@bors bors closed this Jun 13, 2014
@bors bors merged commit b7af250 into rust-lang:master Jun 13, 2014
@alexcrichton alexcrichton deleted the rollup branch June 13, 2014 22:37
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.

10 participants