about summary refs log tree commit diff
path: root/src/test/auxiliary/cci_nested_lib.rs
AgeCommit message (Collapse)AuthorLines
2016-05-06kill the old auxiliary directoryNiko Matsakis-63/+0
2015-03-26Mass rename uint/int to usize/isizeAlex Crichton-4/+4
Now that support has been removed, all lingering use cases are renamed.
2015-02-02`for x in xs.iter()` -> `for x in &xs`Jorge Aparicio-1/+1
2015-01-08fallout: run-pass tests that use box. (many could be ported to `Box::new` ↵Felix S. Klock II-0/+2
instead in the future.)
2014-10-29Rename fail! to panic!Steve Klabnik-1/+1
https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change]
2014-10-02tests: remove uses of Gc.Eduard Burtescu-4/+3
2014-07-26Remove managed_box gate from testsBrian Anderson-1/+0
No longer does anything.
2014-06-14rustc: Obsolete the `@` syntax entirelyAlex Crichton-3/+4
This removes all remnants of `@` pointers from rustc. Additionally, this removes the `GC` structure from the prelude as it seems odd exporting an experimental type in the prelude by default. Closes #14193 [breaking-change]
2014-04-14Use new attribute syntax in python files in src/etc too (#13478)Manish Goregaokar-1/+1
2014-03-22test: Fix fallout of removing get()Alex Crichton-2/+2
2014-03-22Remove outdated and unnecessary std::vec_ng::Vec imports.Huon Wilson-1/+0
(And fix some tests.)
2014-03-21test: Make manual changes to deal with the fallout from removal ofPatrick Walton-0/+1
`~[T]` in test, libgetopts, compiletest, librustdoc, and libnum.
2014-03-21test: Automatically remove all `~[T]` from tests.Patrick Walton-3/+3
2014-01-03test: De-`@mut` the test suitePatrick Walton-5/+15
2013-10-23register snapshotsDaniel Micay-0/+2
2013-10-22Drop the '2' suffix from logging macrosAlex Crichton-1/+1
Who doesn't like a massive renaming?
2013-09-30rpass: Remove usage of fmt!Alex Crichton-1/+1
2013-09-23test: Fix rustdoc and tests.Patrick Walton-1/+1
2013-08-03remove obsolete `foreach` keywordDaniel Micay-1/+1
this has been replaced by `for`
2013-08-01migrate many `for` loops to `foreach`Daniel Micay-1/+1
2013-07-18librustc: Forbid `&` pointers (other than `&'static`) inside `@` boxes.Patrick Walton-4/+8
This makes custom borrowing implementations for custom smart pointers sound.
2013-07-17librustc: Remove all uses of "copy".Patrick Walton-5/+7
2013-06-23vec: remove BaseIter implementationDaniel Micay-1/+1
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.
2013-06-16Add copies to type params with Copy boundNiko Matsakis-1/+1
2013-04-29test: Remove #[legacy_modes] from the test suite.Patrick Walton-8/+12
2013-03-08test: Removing dvec usesAlex Crichton-5/+3
2013-03-02test: Remove `fn@`, `fn~`, and `fn&` from the test suite. rs=defunPatrick Walton-1/+1
2013-03-02librustc: Forbid chained imports and fix the logic for one-level renaming ↵Patrick Walton-1/+1
imports
2013-02-20librustc: Separate most trait bounds with '+'. rs=plussingPatrick Walton-4/+4
2013-02-13Remove die!, raplace invocations with fail! Issue #4524 pt 3Nick Desaulniers-1/+1
2013-01-31Replace most invocations of fail keyword with die! macroNick Desaulniers-1/+1
2013-01-30test: De-export aux, bench, compile-fail, and run-fail. rs=deexportingPatrick Walton-7/+6
2013-01-26testsuite: Eliminate uses of structural records from most run-pass testsTim Chevalier-3/+4
Except the pipes tests (that needs a snapshot)
2013-01-09A collection of refactorings that I found it hard/tiresome to divide:Niko Matsakis-3/+3
- Make `extern fn()` assignable to any closure type, rather than a subtype. - Remove unused int_ty_set and float_ty_set - Refactor variable unification and make it more DRY - Do fn sub/lub/glb on the level of fn_sig - Rename infer::to_str::ToStr to infer::to_str::InferStr - Capitalize names of various types - Correct hashing of FnMeta - Convert various records-of-fns into structs-of-fns. This is both eliminating use of deprecated features and more forwards compatible with fn reform. r=pcwalton
2012-12-10Reliciense makefiles and testsuite. Yup.Graydon Hoare-0/+10
2012-09-24Build the export_map2 from visibility markers, unless #[legacy_exports];Graydon Hoare-0/+1
2012-09-18rustc: Remove legacy mode inference, unless #[legacy_modes] is usedPatrick Walton-1/+3
2012-09-07Convert all kind bounds to camel case. Remove send, owned keywords.Brian Anderson-4/+4
2012-09-05test: "import" -> "use"Patrick Walton-1/+1
2012-08-27Camel case various core constructorsBrian Anderson-3/+3
2012-08-15Convert more core types to camel caseBrian Anderson-2/+2
2012-08-08Convert impls to new syntaxBrian Anderson-1/+1
2012-08-01Convert ret to returnBrian Anderson-3/+3
2012-07-01Convert to new closure syntaxBrian Anderson-1/+1
2012-06-06minor changes to tests so they pass borrowckNiko Matsakis-9/+9
2012-04-06Convert old-style for loops to new-styleMarijn Haverbeke-1/+1
Most could use the each method, but because of the hack used to disambiguate old- and new-style loops, some had to use vec::each. (This hack will go away soon.) Issue #1619
2012-03-07Fix #1941: inlining of items that themselves contain nested itemsNiko Matsakis-0/+29
The fix is to drop nested items from the encoded AST. Nested items may themselves be inlined, but that is an independent question.