- 16 7月, 2014 14 次提交
-
-
由 bors 提交于
This test seems to yield a different error message on cross compiles, so just ignore it when cross compiling.
-
由 bors 提交于
- `width()` computes the displayed width of a string, ignoring the width of control characters. - arguably we might do *something* else for control characters, but the question is, what? - users who want to do something else can iterate over chars() - `graphemes()` returns a `Graphemes` struct, which implements an iterator over the grapheme clusters of a &str. - fully compliant with [UAX#29](http://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) - passes all [Unicode-supplied tests](http://www.unicode.org/reports/tr41/tr41-15.html#Tests29) - added code to generate additionial categories in `unicode.py` - `Cn` aka `Not_Assigned` - categories necessary for grapheme cluster breaking - tidied up the exports from libunicode - all exports are exposed through a module rather than directly at crate root. - std::prelude imports UnicodeChar and UnicodeStrSlice from std::char and std::str rather than directly from libunicode closes #7043
-
由 bors 提交于
-
由 Alex Crichton 提交于
This test seems to yield a different error message on cross compiles, so just ignore it when cross compiling.
-
由 bors 提交于
* Deprecated `str::from_utf8_owned` in favor of `String::from_utf8` * Deprecated `str::from_utf8_lossy` in favor of `String::from_utf8_lossy` * Deprecated `str::from_utf16` in favor of `String::from_utf16` * Deprecated `str::from_utf16_lossy` in favor of `String::from_utf16_lossy` * Deprecated `str::from_chars` in favor of `String::from_chars` * Deprecated `str::from_char` in favor of `String::from_char` and `.to_string()` * Deprecated `str::from_byte` in favor of `String::from_byte` [breaking-change]
-
由 Adolfo Ochagavía 提交于
-
由 Adolfo Ochagavía 提交于
Use `String::from_utf8_lossy` instead [breaking-change]
-
由 Adolfo Ochagavía 提交于
Use `String::from_utf16_lossy` instead. [breaking-change]
-
由 Adolfo Ochagavía 提交于
Use `String::from_utf16` instead [breaking-change]
-
由 Adolfo Ochagavía 提交于
Replaced by `String::from_byte` [breaking-change]
-
由 Adolfo Ochagavía 提交于
Use `String::from_char` or `.to_str` instead [breaking-change]
-
由 Adolfo Ochagavía 提交于
Use `String::from_chars` instead [breaking-change]
-
由 Adolfo Ochagavía 提交于
Use `String::from_utf8` instead [breaking-change]
-
由 bors 提交于
This pull request adds some necessary function definitions and types for doing low level networking with Rust.
-
- 15 7月, 2014 26 次提交
-
-
由 bors 提交于
Signed-off-by: NAnton Lofgren <alofgren@op5.com>
-
由 Robert Clipsham 提交于
* Adds functions for using arbitrary sockets with libuv * Adds types and functions required to support this.
-
由 bors 提交于
Use one or more of the following `-Z` flag options to tell the graphviz renderer to include the corresponding dataflow sets (after the iterative constraint propagation reaches a fixed-point solution): * `-Z flowgraph-print-loans` : loans computed via middle::borrowck * `-Z flowgraph-print-moves` : moves computed via middle::borrowck::move_data * `-Z flowgraph-print-assigns` : assignments, via middle::borrowck::move_data * `-Z flowgraph-print-all` : all of the available sets are included. Fix #15016.
-
由 Felix S. Klock II 提交于
Use one or more of the following `-Z` flag options to tell the graphviz renderer to include the corresponding dataflow sets (after the iterative constraint propagation reaches a fixed-point solution): * `-Z flowgraph-print-loans` : loans computed via middle::borrowck * `-Z flowgraph-print-moves` : moves computed via middle::borrowck::move_data * `-Z flowgraph-print-assigns` : assignments, via middle::borrowck::move_data * `-Z flowgraph-print-all` : all of the available sets are included. Fix #15016. ---- This also adds a module, `syntax::ast_map::blocks`, that captures a common abstraction shared amongst code blocks and procedure-like things. As part of this, moved `ast_map.rs` to subdir `ast_map/mod.rs`, to follow our directory layout conventions. (incorporated review feedback from huon, acrichto.)
-
由 bors 提交于
-
由 bors 提交于
-
由 bors 提交于
This was my weekend project, to start breaking up rustc. It first pulls out LLVM into `rustc_llvm`, then parts of `rustc::back` and `rustc::util` to `rustc_back`. The immediate intent is just to reduce the size of rustc, to reduce memory pressure when building rustc, but this is also a good starting point for further refactoring. The `rustc_back` crate is definitely misnamed (`rustc::back` was never a very cohesive module anyway) - it's mostly just somewhere to stuff parts of rustc that don't have many deps. Right now it's main dep is `syntax`; it has no dep on `rustc_llvm`. Some next steps might be to split `rustc_back` into `rustc_util` (with no `syntax` dep), and `rustc_syntax_util` (with a syntax dep); move the rest of `rustc::util` into `rustc_syntax_util`; move all of `rustc::front` to a new crate, `rustc_front`. At that point the refactoring necessary to keep extracting crates will get harder.
-
由 bors 提交于
-
由 kwantam 提交于
- Graphemes and GraphemeIndices structs implement iterators over grapheme clusters analogous to the Chars and CharOffsets for chars in a string. Iterator and DoubleEndedIterator are available for both. - tidied up the exports for libunicode. crate root exports are now moved into more appropriate module locations: - UnicodeStrSlice, Words, Graphemes, GraphemeIndices are in str module - UnicodeChar exported from char instead of crate root - canonical_combining_class is exported from str rather than crate root Since libunicode's exports have changed, programs that previously relied on the old export locations will need to change their `use` statements to reflect the new ones. See above for more information on where the new exports live. closes #7043 [breaking-change]
-
由 kwantam 提交于
-
由 bors 提交于
Currently when a read-only file has unlink() invoked on it on windows, the call will fail. On unix, however, the call will succeed. In order to have a more consistent behavior across platforms, this error is recognized on windows and the file is changed to read-write before removal is attempted.
-
由 Alex Crichton 提交于
Currently when a read-only file has unlink() invoked on it on windows, the call will fail. On unix, however, the call will succeed. In order to have a more consistent behavior across platforms, this error is recognized on windows and the file is changed to read-write before removal is attempted.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
This makes it much saner for clients to use the library since they don't have to worry about shadowing one llvm with another.
-
由 Brian Anderson 提交于
Just some leftover junk from extracting llvm.
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 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 提交于
-
由 bors 提交于
-