rust/src/test/run-pass/const-enum-vec-ptr.rs, branch 1.23.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.23.02015-06-13T11:55:55+00:00Use `assert_eq!` instead of `assert!` in tests2015-06-13T11:55:55+00:00petrochenkovvadim.petrochenkov@gmail.com2015-06-07T18:00:38+00:00urn:sha1:bddb685e7322c8ffb9578ae9e5a3a161071b257bRemove pretty-expanded from failing tests2015-04-09T00:21:34+00:00Alex Crichtonalex@alexcrichton.com2015-04-08T23:27:10+00:00urn:sha1:ec7c800d2fc0dc5918d325ae68d88c9708d20259
This commit removes pretty-expanded from all tests that wind up calling panic!
one way or another now that its internals are unstable.
Mass rename uint/int to usize/isize2015-03-26T19:10:22+00:00Alex Crichtonalex@alexcrichton.com2015-03-26T00:06:52+00:00urn:sha1:43bfaa4a336095eb5697fb2df50909fd3c72ed14
Now that support has been removed, all lingering use cases are renamed.
rustdoc: Replace no-pretty-expanded with pretty-expanded2015-03-23T21:40:26+00:00Brian Andersonbanderson@mozilla.com2015-03-22T20:13:15+00:00urn:sha1:8c93a79e387f5197e8b8fe73b3d87d2b101b7c4a
Now that features must be declared expanded source often does not compile.
This adds 'pretty-expanded' to a bunch of test cases that still work.
Switch to purely namespaced enums2014-11-17T15:35:51+00:00Steven Facklersfackler@gmail.com2014-11-06T08:05:53+00:00urn:sha1:3dcd2157403163789aaf21a9ab3c4d30a7c6494d
This breaks code that referred to variant names in the same namespace as
their enum. Reexport the variants in the old location or alter code to
refer to the new locations:
```
pub enum Foo {
A,
B
}
fn main() {
let a = A;
}
```
=>
```
pub use self::Foo::{A, B};
pub enum Foo {
A,
B
}
fn main() {
let a = A;
}
```
or
```
pub enum Foo {
A,
B
}
fn main() {
let a = Foo::A;
}
```
[breaking-change]
Rename fail! to panic!2014-10-29T15:43:07+00:00Steve Klabniksteve@steveklabnik.com2014-10-09T19:17:22+00:00urn:sha1:7828c3dd2858d8f3a0448484d8093e22719dbda0
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]
Drop the '2' suffix from logging macros2013-10-22T15:09:56+00:00Alex Crichtonalex@alexcrichton.com2013-10-21T20:08:31+00:00urn:sha1:daf5f5a4d10513ff42e79fa7ef8819b170f3a13d
Who doesn't like a massive renaming?
rpass: Remove usage of fmt!2013-10-01T06:21:19+00:00Alex Crichtonalex@alexcrichton.com2013-09-30T02:23:57+00:00urn:sha1:630082ca8946ff2d0e814a73a2594ba65e1b29beadd gitattributes and fix whitespace issues2013-05-04T00:01:42+00:00Daniel Micaydanielmicay@gmail.com2013-05-03T23:25:04+00:00urn:sha1:86efd97a10fda1f81f5bead0de36e3343a9faa0elibrustc: Remove `fail_unless!`2013-03-29T23:39:08+00:00Patrick Waltonpcwalton@mimiga.net2013-03-29T01:39:09+00:00urn:sha1:1e91595520d0538e6003dc9186f1b0df5c25b77a