summary refs log tree commit diff
path: root/src/test/compile-fail/huge-array-simple.rs
AgeCommit message (Collapse)AuthorLines
2015-04-01dealing with fallout to the tests, in particular diffs between 32- vs 64-bit ↵Felix S. Klock II-3/+6
targets. See also #23926.
2015-04-01Fixes to compile-fail error messages post-rebase.Felix S. Klock II-2/+4
2015-03-02Enable recursion for visit_ty in lint visitorIvan Petkov-0/+1
* The lint visitor's visit_ty method did not recurse, and had a reference to the now closed #10894 * The newly enabled recursion has only affected the `deprectated` lint which now detects uses of deprecated items in trait impls and function return types * Renamed some references to `CowString` and `CowVec` to `Cow<str>` and `Cow<[T]>`, respectively, which appear outside of the crate which defines them * Replaced a few instances of `InvariantType<T>` with `PhantomData<Cell<T>>` * Disabled the `deprecated` lint in several places that reference/implement traits on deprecated items which will get cleaned up in the future * Disabled the `exceeding_bitshifts` lint for compile-fail/huge-array-simple test so it doesn't shadow the expected error on 32bit systems * Unfortunately, this means that if a library declares `#![deny(deprecated)]` and marks anything as deprecated, it will have to disable the lint for any uses of said item, e.g. any impl the now deprecated item For any library that denies deprecated items but has deprecated items of its own, this is a [breaking-change]
2015-01-08Update compile fail tests to use usize.Huon Wilson-1/+1
2014-12-20Allow use of `[_ ; n]` syntax for fixed length and repeating arrays.Nick Cameron-1/+1
This does NOT break any existing programs because the `[_, ..n]` syntax is also supported.
2014-11-01Add lint for checking exceeding bitshifts #17713Falco Hirschenberger-1/+1
2014-10-17Make the tests green as they should on 32-bit architecturesAriel Ben-Yehuda-1/+1
On 32-bit architectures, the size calculations on two of the tests wrap-around in typeck, which gives the relevant arrays a size of 0, which is (correctly) successfully allocated.
2014-10-15response for review commentsAriel Ben-Yehuda-0/+15