about summary refs log tree commit diff
path: root/src/test/run-fail/vec-overrun.rs
AgeCommit message (Collapse)AuthorLines
2020-05-06Move tests from `test/run-fail` to UIYuki Okushi-11/+0
2018-12-25Remove licensesMark Rousskov-10/+0
2016-06-06run rustfmt on test/run-fail folderSrinivas Reddy Thatiparthy-1/+1
2015-03-26Mass rename uint/int to usize/isizeAlex Crichton-2/+2
Now that support has been removed, all lingering use cases are renamed.
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-19Remove a large amount of deprecated functionalityAlex Crichton-2/+2
Spring cleaning is here! In the Fall! This commit removes quite a large amount of deprecated functionality from the standard libraries. I tried to ensure that only old deprecated functionality was removed. This is removing lots and lots of deprecated features, so this is a breaking change. Please consult the deprecation messages of the deleted code to see how to migrate code forward if it still needs migration. [breaking-change]
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-4/+6
`~[T]` in test, libgetopts, compiletest, librustdoc, and libnum.
2014-03-21test: Automatically remove all `~[T]` from tests.Patrick Walton-1/+1
2013-10-25Remove ancient emacs mode lines from test casesBrian Anderson-1/+0
These are relics that serve no purpose.
2013-05-19Use assert_eq! rather than assert! where possibleCorey Richardson-2/+2
2013-03-29librustc: Remove `fail_unless!`Patrick Walton-2/+2
2013-03-07librustc: Convert all uses of `assert` over to `fail_unless!`Patrick Walton-2/+2
2012-12-10Reliciense makefiles and testsuite. Yup.Graydon Hoare-0/+10
2012-09-30When a vec/str bounds check fails, include the bad index and the length of ↵Gareth Daniel Smith-1/+1
the str/vec in the fail message.
2012-06-29Switch the compiler over to using ~[] notation instead of []/~. Closes #2759.Michael Sullivan-1/+1
2012-06-25Make vectors uglier ([]/~). Sorry. Should be temporary. Closes #2725.Michael Sullivan-1/+1
2011-09-11Begin valgrinding some run-fail tests that unwind correctlyBrian Anderson-1/+0
Issue #236
2011-08-20ReformatBrian Anderson-3/+3
This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-08-16Port the tests to the typaram foo<T> syntax.Erick Tryzelaar-1/+1
2011-08-12Convert most working tests to ivecsBrian Anderson-1/+1
I tried to pay attention to what was actually being tested so, e.g. when I test was just using a vec as a boxed thing, I converted to boxed ints, etc. Haven't converted the macro tests yet. Not sure what to do there.
2011-08-10Begin valgrinding run-fail testsBrian Anderson-3/+1
Introduce a temporary no-valgrind directive for the few that aren't clean
2011-07-27Reformat for new syntaxMarijn Haverbeke-2/+2
2011-06-15Reformat source tree (minus a couple tests that are still grumpy).Graydon Hoare-7/+10
2011-05-24test: Fix run-fail testing and bring tests up to dateBrian Anderson-3/+0
A typo in the Makefile was causing these to not run. Happily, a lot of these tests pass, so un-xfailed.
2011-05-16Rewrite everything to use [] instead of vec() in value position.Graydon Hoare-1/+1
2011-05-12Fix mistaken replacements in error-pattern comments in testsMarijn Haverbeke-1/+1
2011-05-12Downcase std modules again, move to :: for module dereferencingMarijn Haverbeke-1/+1
This should be a snapshot transition.
2011-05-03Assume xfail-stage0 implies stage1 and stage2 in tests, for now.Graydon Hoare-0/+2
2011-05-02Un-revert "Use different syntax for checks that matter to typestate", fixing ↵Patrick Walton-2/+2
the problem. This reverts commit d08b443fffb1181d8d45ae5d061412f202dd4118.
2011-05-02Revert "Use different syntax for checks that matter to typestate"Graydon Hoare-2/+2
This reverts commit aa25f22f197682de3b18fc4c8ba068d1feda220f. It broke stage2, not sure why yet.
2011-05-02Use different syntax for checks that matter to typestateTim Chevalier-2/+2
This giant commit changes the syntax of Rust to use "assert" for "check" expressions that didn't mean anything to the typestate system, and continue using "check" for checks that are used as part of typestate checking. Most of the changes are just replacing "check" with "assert" in test cases and rustc.
2011-03-25Switch xfail system to use comments embedded in source files.Graydon Hoare-0/+1
2010-06-23Populate tree.Graydon Hoare-0/+11