- 15 7月, 2014 8 次提交
-
-
由 Brian Anderson 提交于
Indicate that anything that can be extracted here should and that things with syntax deps should be split out someday.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
It is a wrapper around LLVM.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
- 14 7月, 2014 23 次提交
-
-
由 bors 提交于
Not sure how to test this correctly I assume the current tests pass now because of the crate boundaries [and that this is fallout from private by default]?
-
由 bors 提交于
I saw that it was bounded by `Show` but the implication is no guarantee (and had only 0.10 to test, where this behavior has been added to 0.11)
-
由 masklinn 提交于
It is implied by the Show bound, but that implication can be missed.
-
由 James Lal 提交于
-
由 bors 提交于
-
由 bors 提交于
- for 3 implementations of into_maybe_owned() - is_slice() - is_owned()
-
由 bors 提交于
This patch adds doc examples for the make_absolute, change_dir, errors_string and args functions in the os module.
-
由 Erick Tryzelaar 提交于
-
由 bors 提交于
In order to have the spawning semantics be the same for unix/windows, the child's PATH environment variable needs to be searched rather than the parent's environment variable. If the child is inheriting the parent's PATH, then no action need be taken as windows will do the heavy lifting. If the child specifies its own PATH, then it is searched beforehand for the target program and the result is favored if a hit is found. cc #15149, but does not close the issue because libgreen still needs to be updated.
-
由 Alex Crichton 提交于
In order to have the spawning semantics be the same for unix/windows, the child's PATH environment variable needs to be searched rather than the parent's environment variable. If the child is inheriting the parent's PATH, then no action need be taken as windows will do the heavy lifting. If the child specifies its own PATH, then it is searched beforehand for the target program and the result is favored if a hit is found. cc #15149, but does not close the issue because libgreen still needs to be updated.
-
由 bors 提交于
This PR is the outcome of the library stabilization meeting for the `liballoc::owned` and `libcore::cell` modules. Aside from the stability attributes, there are a few breaking changes: * The `owned` modules is now named `boxed`, to better represent its contents. (`box` was unavailable, since it's a keyword.) This will help avoid the misconception that `Box` plays a special role wrt ownership. * The `AnyOwnExt` extension trait is renamed to `BoxAny`, and its `move` method is renamed to `downcast`, in both cases to improve clarity. * The recently-added `AnySendOwnExt` extension trait is removed; it was not being used and is unnecessary. [breaking-change]
-
由 Aaron Turon 提交于
This PR is the outcome of the library stabilization meeting for the `liballoc::owned` and `libcore::cell` modules. Aside from the stability attributes, there are a few breaking changes: * The `owned` modules is now named `boxed`, to better represent its contents. (`box` was unavailable, since it's a keyword.) This will help avoid the misconception that `Box` plays a special role wrt ownership. * The `AnyOwnExt` extension trait is renamed to `BoxAny`, and its `move` method is renamed to `downcast`, in both cases to improve clarity. * The recently-added `AnySendOwnExt` extension trait is removed; it was not being used and is unnecessary. [breaking-change]
-
由 Anton Lofgren 提交于
This patch adds doc examples for the make_absolute, change_dir, errors_string and args functions in the os module.
-
由 bors 提交于
This patch adds support for macros in method position. It follows roughly the template for Item macros, where an outer `Method` wrapper contains a `Method_` enum which can either be a macro invocation or a standard macro definition. One note; adding support for macros that expand into multiple methods is not included here, but should be a simple parser change, since this patch updates the type of fold_macro to return a smallvector of methods. For reviewers, please pay special attention to the parser changes; these are the ones I'm most concerned about. Because of the small change to the interface of fold_method, this is a ... [breaking change]
-
由 John Clements 提交于
Closes #4621
-
由 John Clements 提交于
-
由 John Clements 提交于
this allows macro results to be parsed as methods
-
由 John Clements 提交于
-
由 John Clements 提交于
nothing wrong with a statement expanding into 0 stmts, that I can see.
-
由 John Clements 提交于
This is nice for macros, to allow them to expand into multiple methods
-
由 John Clements 提交于
-
由 John Clements 提交于
-
由 John Clements 提交于
This change propagates to many locations, but because of the Macro Exterminator (or, more properly, the invariant that it protects), macro invocations can't occur downstream of expansion. This means that in librustc and librustdoc, extracting the desired field can simply assume that it can't be a macro invocation. Functions in ast_util abstract over this check.
-
- 13 7月, 2014 9 次提交
-
-
由 bors 提交于
The new iterator takes a function and produces an infinite stream of results of repeated applications of the function, starting from the provided seed value.
-
由 Jakub Wieczorek 提交于
Implementation by Kevin Ballard. The function returns an Unfold iterator producing an infinite stream of results of repeated applications of the function, starting from the provided seed value.
-
由 bors 提交于
* Fixes a typo in the libstd documentation, referring UPD instead of UDP
-
由 bors 提交于
cc #15294
-
由 nham 提交于
-
由 bors 提交于
* Don't warn about `#[crate_name]` if `--crate-name` is specified * Don't warn about non camel case identifiers on `#[repr(C)]` structs * Switch `mode` to `mode_t` in libc.
-
由 Corey Richardson 提交于
-
由 bors 提交于
They used to be one token too long, so you'd see things like ``` rust/rust/test.rs:1:1: 2:2 warning: unused attribute, rust/rust/test.rs:1 #![foo] rust/rust/test.rs:2 #![bar] ``` instead of ``` test.rs:1:1: 1:8 warning: unused attribute, #[warn(unused_attribute)] on by default test.rs:1 #![foo] ^~~~~~~ ```
-
由 bors 提交于
This fixes #15474
-