- 17 7月, 2014 7 次提交
-
-
由 Patrick Walton 提交于
This makes two changes to region inference: (1) it allows region inference to relate early-bound regions; and (2) it allows regions to be related before variance runs. The former is needed because there is no relation between the two regions before region substitution happens, while the latter is needed because type collection has to run before variance. We assume that, before variance is inferred, that lifetimes are invariant. This is a conservative overapproximation. This relates to #13885. This does not remove `~self` from the language yet, however. [breaking-change]
-
由 bors 提交于
-
由 Nick Cameron 提交于
-
由 bors 提交于
Disabling the redzone is required in x86-64's kernel mode to avoid interrupts trashing the stack. I'm not sure if decl_fn is the right place to tag all functions with noredzone. It might have interactions with external functions when linking with bitcode built without -C no-redzone although I see no reason to do that. I'm not sure how to write a test inspecting the bitcode output for noredzone attributes on all functions either.
-
由 Nick Cameron 提交于
-
由 bors 提交于
Example code for HashSet, similar to the [HashMap example](http://doc.rust-lang.org/std/collections/hashmap/struct.HashMap.html).
-
由 bors 提交于
This PR adds the LLDB autotests to the debuginfo test suite so I don't have to keep rebasing them locally. They are still disabled by default in `tests.mk`. One of the commits also contains a Python pretty printer which can make LLDB print values with Rust syntax. This was mainly added to deal with output format differences between LLDB versions but you can also use it for your normal LLDB debugging sessions. ``` // The following LLDB commands will load and activate the Rust printers command script import ./src/etc/lldb_rust_formatters.py type summary add --no-value --python-function lldb_rust_formatters.print_val -x .* --category Rust type category enable Rust ``` Expect some rough edges with these, they have not been tested apart from there use in the autotests...
-
- 16 7月, 2014 33 次提交
-
-
由 bors 提交于
Tweak the text editing settings (softtabstop, textwidth, etc). Add some settings to turn on folding and colorcolumn. Add the undo_ftplugin changes that my previous patch forgot.
-
由 Jonas Hietala 提交于
Add main example and simple examples for the methods.
-
由 bors 提交于
Cargo now comes with Rust!
-
由 John Kåre Alsaker 提交于
Disabling the redzone is required in x86-64's kernel mode to avoid interrupts trashing the stack.
-
由 bors 提交于
This patch applies the excellent suggestion of @pnkfelix to group the helper methods for method field access into a Trait, making the code much more readable, and much more similar to the way it was before.
-
由 Michael Woerister 提交于
Some older versions of LLDB have problems with multiple instances running in parallel. This commit makes sure we don't do that.
-
由 Michael Woerister 提交于
This commit adds LLDB autotests to the test suite but does not activate them by default yet.
-
由 Michael Woerister 提交于
The shutdown call would always result in an exception being printed to standard error.
-
由 Michael Woerister 提交于
-
由 Michael Woerister 提交于
-
由 bors 提交于
Closes #15525 The important bit of this are the changes from line 445 in mem_categorization.rs. Most of the other changes are about adding an Implicit PointerKind, and this is only necessary for getting a decent error message :-s An alternative would have been to add an implciti/explicit flag to cat_deref, which could be mostly ignored and so would mean much fewer changes. However, the implicit state would only be valid if the PointerKind was BorrowedPtr, so it felt like it ought to be another kind of PointerKind. I still don't know which is the better design.
-
由 bors 提交于
This branch has a fix for #15557 (a2bcef9) as well as a variety of patches I found useful while debugging this issue. These include adding `Show` impls to a variety of types, including the majority of `syntax::ast` and some of `middle::ty`.
-
由 bors 提交于
This test seems to yield a different error message on cross compiles, so just ignore it when cross compiling.
-
由 Ben Gamari 提交于
-
由 Ben Gamari 提交于
-
由 Ben Gamari 提交于
To verify that a type can satisfy Send `check_struct_safe_for_destructor` attempts to construct a new `ty::t` an empty substitution list. Previously the function would verify that the function has no type parameters before attempting this. Unfortunately this check would not catch functions with only regions parameters. In this case, the type would eventually find its way to the substition engine which would attempt to perform a substitution on the region parameters. As the constructed substitution list is empty, this would fail, leading to a compiler crash. We fix this by verifying that types have both no type and region parameters.
-
由 Ben Gamari 提交于
-
由 Ben Gamari 提交于
Previously this was an Option::unwrap() which failed for me. Unfortunately I've since inadvertently worked around the bug and have been unable to reproduce it. With this patch hopefully the next person to encounter this will be in a slightly better position to debug it.
-
由 Ben Gamari 提交于
And change some uses of the `{:?}` format string to `{}`.
-
由 Ben Gamari 提交于
-
由 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
-
由 John Clements 提交于
Per @pnkfelix 's suggestion, using a trait to make these field accesses more readable (and vastly more similar to the original code. oops fix new ast_map fix
-
由 John Clements 提交于
please note the snapshot-waiting unpleasantness. I'm unable to use the traditional #[cfg(stage0)] mechanism to swap the new style in for later compiler stages, because macros invocations in method positions cause the parser to choke before cfg can strip it out. Parenthetical note: this problem wouldn't arise with an interleaved parsing/expansion....
-
由 bors 提交于
-
由 Alex Crichton 提交于
This test seems to yield a different error message on cross compiles, so just ignore it when cross compiling.
-
由 Steve Klabnik 提交于
Cargo now comes with Rust
-
由 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]
-