- 03 1月, 2014 1 次提交
-
-
由 Patrick Walton 提交于
-
- 30 12月, 2013 1 次提交
-
-
由 Steven Fackler 提交于
-
- 29 12月, 2013 1 次提交
-
-
由 Steven Fackler 提交于
-
- 12 12月, 2013 1 次提交
-
-
由 Erik Price 提交于
Also remove all instances of 'self within the codebase. This fixes #10889.
-
- 10 12月, 2013 1 次提交
-
-
由 Seo Sanghyeon 提交于
-
- 08 12月, 2013 1 次提交
-
-
由 Kiet Tran 提交于
-
- 29 11月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
-
- 22 10月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
Who doesn't like a massive renaming?
-
- 08 10月, 2013 2 次提交
-
-
由 Benjamin Herr 提交于
For the benefit of the pretty printer we want to keep track of how string literals in the ast were originally represented in the source code. This commit changes parser functions so they don't extract strings from the token stream without at least also returning what style of string literal it was. This is stored in the resulting ast node for string literals, obviously, for the package id in `extern mod = r"package id"` view items, for the inline asm in `asm!()` invocations. For `asm!()`'s other arguments or for `extern "Rust" fn()` items, I just the style of string, because it seemed disproportionally cumbersome to thread that information through the string processing that happens with those string literals, given the limited advantage raw string literals would provide in these positions. The other syntax extensions don't seem to store passed string literals in the ast, so they also discard the style of strings they parse.
-
由 Benjamin Herr 提交于
Treat it as a synonym for LIT_STR for now.
-
- 02 10月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
It is simply defined as `f64` across every platform right now. A use case hasn't been presented for a `float` type defined as the highest precision floating point type implemented in hardware on the platform. Performance-wise, using the smallest precision correct for the use case greatly saves on cache space and allows for fitting more numbers into SSE/AVX registers. If there was a use case, this could be implemented as simply a type alias or a struct thanks to `#[cfg(...)]`. Closes #6592 The mailing list thread, for reference: https://mail.mozilla.org/pipermail/rust-dev/2013-July/004632.html
-
- 01 10月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
-
- 07 9月, 2013 2 次提交
-
-
由 John Clements 提交于
This is actually almost a problem, because those were my poster-child macros for "here's how to implement a capturing macro." Following this change, there will be no macros that use capturing; this will probably make life unpleasant for the first person that wants to implement a capturing macro. I should probably create a dummy_capturing macro, just to show how it works.
-
由 John Clements 提交于
-
- 04 9月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
Closes #7609
-
- 03 9月, 2013 1 次提交
-
-
由 Marvin Löbel 提交于
-
- 02 9月, 2013 1 次提交
-
-
由 Marvin Löbel 提交于
-
- 01 9月, 2013 1 次提交
-
-
由 Marvin Löbel 提交于
-
- 19 8月, 2013 1 次提交
-
-
由 Steven Fackler 提交于
They previously required one called "ext_cx" to be in scope. Fixes part of #7727
-
- 13 8月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
Closes #5495
-
- 04 8月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
this has been replaced by `for`
-
- 02 8月, 2013 2 次提交
-
-
由 OGINO Masanori 提交于
I didn't rename variables because they are local and are not parts of the public interfaces. Signed-off-by: NOGINO Masanori <masanori.ogino@gmail.com>
-
由 Brian Anderson 提交于
The pipes compiler produced data types that encoded efficient and safe bounded message passing protocols between two endpoints. It was also capable of producing unbounded protocols. It was useful research but was arguably done before its proper time. I am removing it for the following reasons: * In practice we used it only for producing the `oneshot` and `stream` unbounded protocols and all communication in Rust use those. * The interface between the proto! macro and the standard library has a large surface area and was difficult to maintain through language and library changes. * It is now written in an old dialect of Rust and generates code which would likely be considered non-idiomatic. * Both the compiler and the runtime are difficult to understand, and likewise the relationship between the generated code and the library is hard to understand. Debugging is difficult. * The new scheduler implements `stream` and `oneshot` by hand in a way that will be significantly easier to maintain. This shouldn't be taken as an indication that 'channel protocols' for Rust are not worth pursuing again in the future.
-
- 01 8月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
-
- 22 7月, 2013 1 次提交
-
-
由 Michael Woerister 提交于
`crate => Crate` `local => Local` `blk => Block` `crate_num => CrateNum` `crate_cfg => CrateConfig` Also, Crate and Local are not wrapped in spanned<T> anymore.
-
- 18 7月, 2013 2 次提交
-
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
- 13 7月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
-
- 07 7月, 2013 1 次提交
-
-
由 James Miller 提交于
-
- 26 6月, 2013 1 次提交
-
-
由 Corey Richardson 提交于
-
- 23 6月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
I removed the `static-method-test.rs` test because it was heavily based on `BaseIter` and there are plenty of other more complex uses of static methods anyway.
-
- 16 6月, 2013 1 次提交
-
-
由 Huon Wilson 提交于
-
- 14 6月, 2013 1 次提交
-
-
由 Brian Anderson 提交于
This fixes the strange random crashes in compile-fail tests. This reverts commit 96cd61ad. Conflicts: src/librustc/driver/driver.rs src/libstd/str.rs src/libsyntax/ext/quote.rs
-
- 13 6月, 2013 1 次提交
-
-
由 Huon Wilson 提交于
This almost removes the StringRef wrapper, since all strings are Equiv-alent now. Removes a lot of `/* bad */ copy *`'s, and converts several things to be &'static str (the lint table and the intrinsics table). There are many instances of .to_managed(), unfortunately.
-
- 12 6月, 2013 2 次提交
-
-
由 Huon Wilson 提交于
The first acts on &str and is not nul-terminated, the last two act on strings that are always null terminated (&'static str, ~str and @str).
-
由 Huon Wilson 提交于
-
- 10 6月, 2013 1 次提交
-
-
由 Huon Wilson 提交于
-
- 07 6月, 2013 1 次提交
-
-
由 Michael Sullivan 提交于
-
- 06 6月, 2013 2 次提交
-
-
由 John Clements 提交于
-
由 John Clements 提交于
-