about summary refs log tree commit diff
path: root/src/test/auxiliary
AgeCommit message (Collapse)AuthorLines
2015-02-17Fallout from stabilizationAaron Turon-2/+2
2015-02-17Rollup merge of #22364 - Manishearth:rfc-572-forbid-attr, r=nikomatsakisManish Goregaokar-20/+0
fixes #22203 r? @nikomatsakis This breaks code that might be using attributes randomly, so it's technically a [breaking-change]
2015-02-17Rollup merge of #22418 - japaric:diagnostics, r=nikomatsakisManish Goregaokar-0/+11
closes #22388 r? @nikomatsakis cc @insaneinside
2015-02-17Rollup merge of #22241 - kmcallister:macro-plugin-cleanup, r=sfacklerManish Goregaokar-0/+22
2015-02-16Make orphan check diagnostics clearerJorge Aparicio-0/+11
closes #22388
2015-02-16Remove obsolete stability attrs from testManish Goregaokar-20/+0
2015-02-13Auto merge of #22093 - petrochenkov:builtin, r=pnkfelixbors-0/+13
Names of structs, enums, traits, type aliases and type parameters (i.e. all identifiers that can be used as full paths in type position) are not allowed to match the names of primitive types. See #20427 for more information. This is a minor [breaking-change]
2015-02-12Warn when linking a plugin into a non-plugin crateKeegan McAllister-0/+22
Fixes #22202.
2015-02-11rollup merge of #22178: pnkfelix/featuregate-unsafe-no-drop-flagAlex Crichton-0/+2
Conflicts: src/libsyntax/feature_gate.rs
2015-02-11Feature-gate the `#[unsafe_no_drop_flag]` attribute.Felix S. Klock II-0/+2
See RFC 320, "Non-zeroing dynamic drops." Fix #22173 [breaking-change]
2015-02-11shift bindings to accommodate new lifetime/dtor rules.Felix S. Klock II-1/+2
(My fix to for-loops (21984) did not deal with similar problems in if-let expressions, so those binding shifts stay.)
2015-02-09Use a crate attribute to load pluginsKeegan McAllister-6/+5
#[plugin] #[no_link] extern crate bleh; becomes a crate attribute #![plugin(bleh)] The feature gate is still required. It's almost never correct to link a plugin into the resulting library / executable, because it will bring all of libsyntax and librustc with it. However if you really want this behavior, you can get it with a separate `extern crate` item in addition to the `plugin` attribute. Fixes #21043. Fixes #20769. [breaking-change]
2015-02-08Fix issue #20427we-0/+13
2015-02-08Auto merge of #22054 - LeoTestard:include-parse-errors, r=alexcrichtonbors-0/+13
Makes the compilation abort when a parse error is encountered while trying to parse an item in an included file. The previous behaviour was to stop processing the file when a token that can't start an item was encountered, without producing any error. Fixes #21146.
2015-02-07Feature-gate #![no_std]Keegan McAllister-0/+3
Fixes #21833. [breaking-change]
2015-02-07Fix handling of parse errors when using `include!()`.Leo Testard-0/+13
Makes the compilation abort when a parse error is encountered while trying to parse an item in an included file. The previous behaviour was to stop processing the file when a token that can't start an item was encountered, without producing any error. Fixes #21146.
2015-02-06librustdoc has been updatedGuillaumeGomez-3/+3
Fixes run build error Fix test failure Fix tests' errors
2015-02-05cleanup: replace `as[_mut]_slice()` calls with deref coercionsJorge Aparicio-3/+3
2015-02-04remove all kind annotations from closuresJorge Aparicio-6/+6
2015-02-04Fix testManish Goregaokar-10/+3
2015-02-03Auto merge of #21675 - huonw:less-false-positives, r=nikomatsakisbors-0/+3
That is, when offering suggestions for unresolved method calls, avoid suggesting traits for which implementing the trait for the receiver type either makes little sense (e.g. type errors, or sugared unboxed closures), or violates coherence. The latter is approximated by ensuring that at least one of `{receiver type, trait}` is local. This isn't precisely correct due to multidispatch, but the error messages one encounters in such situation are useless more often than not; it is better to be conservative and miss some cases, than have overly many false positives (e.g. writing `some_slice.map(|x| ...)` uselessly suggested that one should implement `IteratorExt` for `&[T]`, while the correct fix is to call `.iter()`). Closes #21420.
2015-02-03Try to only suggest implementable traits for method calls.Huon Wilson-0/+3
That is, when offering suggestions for unresolved method calls, avoid suggesting traits for which implementing the trait for the receiver type either makes little sense (e.g. type errors, or sugared unboxed closures), or violates coherence. The latter is approximated by ensuring that at least one of `{receiver type, trait}` is local. This isn't precisely correct due to multidispatch, but the error messages one encounters in such situation are useless more often than not; it is better to be conservative and miss some cases, than have overly many false positives (e.g. writing `some_slice.map(|x| ...)` uselessly suggested that one should implement `IteratorExt` for `&[T]`, while the correct fix is to call `.iter()`). Closes #21420.
2015-02-02`for x in xs.iter()` -> `for x in &xs`Jorge Aparicio-1/+1
2015-01-31Add tests for MultiItemDecoratorAdolfo Ochagavía-3/+82
2015-01-30rollup merge of #21631: tbu-/isize_policeAlex Crichton-6/+6
Conflicts: src/libcoretest/iter.rs
2015-01-30rollup merge of #21718: alexcrichton/stabilize-from-strAlex Crichton-1/+1
This commits adds an associated type to the `FromStr` trait representing an error payload for parses which do not succeed. The previous return value, `Option<Self>` did not allow for this form of payload. After the associated type was added, the following attributes were applied: * `FromStr` is now stable * `FromStr::Err` is now stable * `FromStr::from_str` is now stable * `StrExt::parse` is now stable * `FromStr for bool` is now stable * `FromStr for $float` is now stable * `FromStr for $integral` is now stable * Errors returned from stable `FromStr` implementations are stable * Errors implement `Display` and `Error` (both impl blocks being `#[stable]`) Closes #15138
2015-01-30rollup merge of #21704: FlaPer87/macro-reexportAlex Crichton-0/+2
Conflicts: src/libstd/lib.rs
2015-01-30std: Stabilize FromStr and parseAlex Crichton-1/+1
This commits adds an associated type to the `FromStr` trait representing an error payload for parses which do not succeed. The previous return value, `Option<Self>` did not allow for this form of payload. After the associated type was added, the following attributes were applied: * `FromStr` is now stable * `FromStr::Err` is now stable * `FromStr::from_str` is now stable * `StrExt::parse` is now stable * `FromStr for bool` is now stable * `FromStr for $float` is now stable * `FromStr for $integral` is now stable * Errors returned from stable `FromStr` implementations are stable * Errors implement `Display` and `Error` (both impl blocks being `#[stable]`) Closes #15138
2015-01-30fix testsJorge Aparicio-1/+1
2015-01-30Remove all `i` suffixesTobias Bucher-6/+6
2015-01-29s/Show/Debug/gJorge Aparicio-1/+1
2015-01-29Feature gate macro_reexport. Fixes #20906Flavio Percoco-0/+2
2015-01-29Auto merge of #21680 - japaric:slice, r=alexcrichtonbors-1/+1
Replaces `slice_*` method calls with slicing syntax, and removes `as_slice()` calls that are redundant due to `Deref`.
2015-01-28Merge remote-tracking branch 'origin/master' into rollupManish Goregaokar-108/+103
Conflicts: src/libcollections/slice.rs src/libcore/nonzero.rs src/libcore/ops.rs
2015-01-27cleanup: s/`v.slice*()`/`&v[a..b]`/g + remove redundant `as_slice()` callsJorge Aparicio-1/+1
2015-01-25cleanup: s/impl Copy/#[derive(Copy)]/gJorge Aparicio-19/+10
2015-01-25Merge remote-tracking branch 'rust-lang/master'Brian Anderson-2/+54
Conflicts: mk/tests.mk src/liballoc/arc.rs src/liballoc/boxed.rs src/liballoc/rc.rs src/libcollections/bit.rs src/libcollections/btree/map.rs src/libcollections/btree/set.rs src/libcollections/dlist.rs src/libcollections/ring_buf.rs src/libcollections/slice.rs src/libcollections/str.rs src/libcollections/string.rs src/libcollections/vec.rs src/libcollections/vec_map.rs src/libcore/any.rs src/libcore/array.rs src/libcore/borrow.rs src/libcore/error.rs src/libcore/fmt/mod.rs src/libcore/iter.rs src/libcore/marker.rs src/libcore/ops.rs src/libcore/result.rs src/libcore/slice.rs src/libcore/str/mod.rs src/libregex/lib.rs src/libregex/re.rs src/librustc/lint/builtin.rs src/libstd/collections/hash/map.rs src/libstd/collections/hash/set.rs src/libstd/sync/mpsc/mod.rs src/libstd/sync/mutex.rs src/libstd/sync/poison.rs src/libstd/sync/rwlock.rs src/libsyntax/feature_gate.rs src/libsyntax/test.rs
2015-01-23grandfathered -> rust1Brian Anderson-17/+17
2015-01-23Fix tidy.Vadim Chugunov-1/+1
2015-01-23Deprecated attributes don't take 'feature' names and are paired with ↵Brian Anderson-12/+57
stable/unstable Conflicts: src/libcore/atomic.rs src/libcore/finally.rs src/test/auxiliary/inherited_stability.rs src/test/auxiliary/lint_stability.rs
2015-01-23Set unstable feature names appropriatelyBrian Anderson-20/+20
* `core` - for the core crate * `hash` - hashing * `io` - io * `path` - path * `alloc` - alloc crate * `rand` - rand crate * `collections` - collections crate * `std_misc` - other parts of std * `test` - test crate * `rustc_private` - everything else
2015-01-22Added test.Vadim Chugunov-0/+26
2015-01-22Put #[staged_api] behind the 'staged_api' gateBrian Anderson-0/+5
2015-01-21Remove 'since' from unstable attributesBrian Anderson-17/+17
2015-01-21Minor fixesBrian Anderson-0/+1
2015-01-21Add 'feature' and 'since' to stability attributesBrian Anderson-111/+55
2015-01-21rollup merge of #20179: eddyb/blind-itemsAlex Crichton-0/+26
Conflicts: src/librustc/diagnostics.rs src/librustdoc/clean/mod.rs src/librustdoc/html/format.rs src/libsyntax/parse/parser.rs
2015-01-21Added some tests for arbitrary ordered view itemsMarvin Löbel-0/+26
2015-01-21rollup merge of #21340: pshc/libsyntax-no-more-intsAlex Crichton-2/+2
Collaboration with @rylev! I didn't change `int` in the [quasi-quoter](https://github.com/pshc/rust/blob/99ae1a30f3ca28c0f7e431620560d30e44627124/src/libsyntax/ext/quote.rs#L328), because I'm not sure if there will be adverse effects. Addresses #21095.
2015-01-18std: Stabilize TypeId and tweak BoxAnyAlex Crichton-23/+21
This commit aims to stabilize the `TypeId` abstraction by moving it out of the `intrinsics` module into the `any` module of the standard library. Specifically, * `TypeId` is now defined at `std::any::TypeId` * `TypeId::hash` has been removed in favor of an implementation of `Hash`. This commit also performs a final pass over the `any` module, confirming the following: * `Any::get_type_id` remains unstable as *usage* of the `Any` trait will likely never require this, and the `Any` trait does not need to be implemented for any other types. As a result, this implementation detail can remain unstable until associated statics are implemented. * `Any::downcast_ref` is now stable * `Any::downcast_mut` is now stable * `BoxAny` remains unstable. While a direct impl on `Box<Any>` is allowed today it does not allow downcasting of trait objects like `Box<Any + Send>` (those returned from `Thread::join`). This is covered by #18737. * `BoxAny::downcast` is now stable.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-25 11:17:30 +0000