- 28 3月, 2014 2 次提交
-
-
由 bors 提交于
A variety of stuff here, mostly aimed at making `make install` work correctly with `--libdir` and `--mandir`. `make install` again goes through `install.sh`.
-
由 bors 提交于
This bench is meant to exercise libgreen, not libnative. It recently caused the auto-linux-32-nopt-t bot to fail as no output was produced for an hour.
-
- 27 3月, 2014 20 次提交
-
-
由 bors 提交于
Closes #6751
-
由 Corey Richardson 提交于
We really do *not* want TCO to kick in. If it does, we'll never blow the stack, and never trigger the condition the test is checking for. To that end, do a meaningless alloc that serves only to get a destructor to run. The addition of nocapture/noalias seems to have let LLVM do more TCO, which hurt this testcase.
-
由 bors 提交于
The `_match.rs` takes advantage of passes prior to `trans` and aggressively prunes the sub-match tree based on exact equality. When it comes to literal or range, the strategy may lead to wrong result if there's guard function or multiple patterns inside tuple. Closes #12582. Closes #13027.
-
由 Corey Richardson 提交于
-
由 Corey Richardson 提交于
Closes #6751
-
由 Edward Wang 提交于
The `_match.rs` takes advantage of passes prior to `trans` and aggressively prunes the sub-match tree based on exact equality. When it comes to literal or range, the strategy may lead to wrong result if there's guard function or multiple patterns inside tuple. Closes #12582. Closes #13027.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 bors 提交于
The previous syntax was `Foo:Bound<trait-parameters>`, but this is a little ambiguous because it was being parsed as `Foo: (Bound<trait-parameters)` rather than `Foo: (Bound) <trait-parameters>` This commit changes the syntax to `Foo<trait-parameters>: Bound` in order to be clear where the trait parameters are going. Closes #9265
-
由 Brian Anderson 提交于
Instead of just looking for its presence we need to see if it actually contains rust stuffs.
-
由 Brian Anderson 提交于
-
由 bors 提交于
This change prepares `rustc` to accept private fields by default. These changes will have to go through a snapshot before the rest of the changes can happen.
-
由 Brian Anderson 提交于
The installed manifest is a different file, so they should have different names. This should prevent various wierd conflicts in the future.
-
由 Alex Crichton 提交于
The previous syntax was `Foo:Bound<trait-parameters>`, but this is a little ambiguous because it was being parsed as `Foo: (Bound<trait-parameters)` rather than `Foo: (Bound) <trait-parameters>` This commit changes the syntax to `Foo<trait-parameters>: Bound` in order to be clear where the trait parameters are going. Closes #9265
-
由 bors 提交于
Add some docs to ExpnInfo. Add a single overlooked `new_span` call to the folder (I'm pretty sure nothing reads this span, though, so it's probably pointless).
-
由 bors 提交于
Close #13057
-
由 Alex Crichton 提交于
This change is in preparation for #8122. Nothing is currently done with these visibility qualifiers, they are just parsed and accepted by the compiler. RFC: 0004-private-fields
-
由 Alex Crichton 提交于
This is a necessary change in preparation for switching the defaults as part of #8122. RFC: 0004-private-fields
-
由 Alex Crichton 提交于
This bench is meant to exercise libgreen, not libnative. It recently caused the auto-linux-32-nopt-t bot to fail as no output was produced for an hour.
-
由 bors 提交于
I touched up the documentation from @pcwalton found in #12952.
-
- 26 3月, 2014 18 次提交
-
-
由 Huon Wilson 提交于
This was leaving Decls without the new spans; this is a minor change, since literally nothing reads in the code base reads the span of a Decl itself, always just its contents.
-
由 Huon Wilson 提交于
-
由 bors 提交于
Apparently we had forgotten to do this for freebsd, causing possible problems on FreeBSD 10. The discussion in #12324 has some more details about how it's missing.
-
由 bors 提交于
The libuv fs wrappers are very thin wrappers around the syscalls they correspond to, and a notable worrisome case is the write syscall. This syscall is not guaranteed to write the entire buffer provided, so we may have to continue calling uv_fs_write if a short write occurs. Closes #13130
-
由 bors 提交于
This can be done now that logging has been moved out and libnative is the default (not libgreen)
-
由 Brian Anderson 提交于
This adds a hack to rustc to make it find the library directory regardless of whether it is named lib/lib64/lib32.
-
由 bors 提交于
# Summary Changed `iter::Extendable` and `iter::FromIterator` to take a `Iterator` by value. These functions always exhaust the passed `Iterator`, and are often used for transferring the values of a new `Iterator` directly into a data structure, so using them usually require the use of the `&mut` operator: ``` foo.extend(&mut bar.move_iter()); // Transfer content from bar into foo let mut iter = ...; foo.extend(&mut iter); // iter is now empty ``` This patch changes both the `FromIterator` and `Extendable` traits to take the iterator by value instead, which makes the common case of using these traits less heavy: ``` foo.extend(bar.move_iter()); // Transfer content from bar into foo let iter = ...; foo.extend(iter); // iter is now inaccessible if it moved // or unchanged if it was Pod and copied. ``` # Composability This technically makes the traits less flexible from a type system pov, because they now require ownership. However, because `Iterator` provides the `ByRef` adapter, there is no loss of functionality: ``` foo.extend(iter.by_ref()); // Same semantic as today, for the few situations where you need it. ``` # Motivation This change makes it less painful to use iterators for shuffling values around between collections, which makes it more acceptable to always use them for this, enabling more flexibility. For example, `foo.extend(bar.move_iter())` can generally be the fastest way to append an collections content to another one, without both needing to have the same type. Making this easy to use would allow the removal of special cased methods like `push_all()` on vectors. (See https://github.com/mozilla/rust/issues/12456) I opened https://github.com/mozilla/rust/issues/13038 as well, to discuss this change in general if people object to it. # Further work This didn't change the `collect()` method to take by value `self`, nor any of the other adapters that also exhaust their iterator argument. For consistency this should probably happen in the long term, but for now this is too much trouble, as every use of them would need to be checked for accidentally changed semantic by going `&mut self -> self`. (which allows for the possibility that a `Pod` iterator got copied instead of exhausted without generating a type error by the change)
-
由 bors 提交于
* Include tip given by Leo Testard in mailing list about labeled `break` and `continue`: https://mail.mozilla.org/pipermail/rust-dev/2014-March/009145.html * cross-reference named lifetimes in tutorial -> lifetimes guide * Broke named lifetimes section into two sub-sections. * Added mention of `'static` lifetime.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
Much clearer
-
由 Brian Anderson 提交于
This is not sufficient for finding the library directory for binary installs, but it does make the build more complex by requiring env vars be set to build rustc.
-
由 Brian Anderson 提交于
Trying to reduce the complexity of installation
-
由 Brian Anderson 提交于
This reverts commit d6216318. Conflicts: mk/install.mk
-
由 Brian Anderson 提交于
-
由 bors 提交于
-
由 Brian Anderson 提交于
-
由 bors 提交于
Rendered form available at http://docs.octayn.net/doc/ This moves derived impls to the bottom of the list, separate from the rest, and collapses default methods that aren't overridden into an expandible accordion.
-