rust/src/libcoretest/num/uint_macros.rs, branch 1.0.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.0.02015-04-23T22:18:14+00:00std: Bring back f32::from_str_radix as an unstable API2015-04-23T22:18:14+00:00Alex Crichtonalex@alexcrichton.com2015-04-18T06:45:55+00:00urn:sha1:1c9aa362292555566e4ff8366f574b70ff59d5c8
This API was exercised in a few tests and mirrors the `from_str_radix`
functionality of the integer types.
Conflicts:
src/doc/trpl/traits.md
src/libstd/sys/windows/fs2.rs
Auto merge of #23832 - petrochenkov:usize, r=aturon2015-04-03T04:29:52+00:00borsbors@rust-lang.org2015-04-03T04:29:52+00:00urn:sha1:fc98b19cf72ea45851ebb7b28af160be92b19128
These constants are small and can fit even in `u8`, but semantically they have type `usize` because they denote sizes and are almost always used in `usize` context. The change of their type to `u32` during the integer audit led only to the large amount of `as usize` noise (see the second commit, which removes this noise).
This is a minor [breaking-change] to an unstable interface.
r? @aturon
Fallout from changes for overflow-checking during constant evaluation.2015-04-01T00:56:07+00:00Felix S. Klock IIpnkfelix@pnkfx.org2015-03-29T23:23:15+00:00urn:sha1:8d54ea3ec9c48eaeaab8fa9061cf28c2678e8ae9Fix the fallout2015-03-30T09:19:11+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2015-03-28T17:22:48+00:00urn:sha1:883adc6763c3dd06b282368698b28a07cdd65fd6Use `const`s instead of `static`s where appropriate2015-03-02T16:11:51+00:00Florian Zeitzflorob@babelmonkeys.de2015-02-27T14:36:53+00:00urn:sha1:f35f973cb700c444d8c029ee13b37dc16d560225
This changes the type of some public constants/statics in libunicode.
Notably some `&'static &'static [(char, char)]` have changed
to `&'static [(char, char)]`. The regexp crate seems to be the
sole user of these, yet this is technically a [breaking-change]
Deprecating i/u suffixes in libcoretest2015-02-10T22:56:31+00:00Alfie Johnalfiej@fastmail.fm2015-02-03T13:50:52+00:00urn:sha1:bffbcb5729a2b4cb2ab924e5f0d9ddebe470eebcModernize macro_rules! invocations2015-01-06T02:21:14+00:00Keegan McAllisterkmcallister@mozilla.com2015-01-02T22:44:21+00:00urn:sha1:416137eb3186c05b7a601e94cde354e9b3ec0a78
macro_rules! is like an item that defines a macro. Other items don't have a
trailing semicolon, or use a paren-delimited body.
If there's an argument for matching the invocation syntax, e.g. parentheses for
an expr macro, then I think that applies more strongly to the *inner*
delimiters on the LHS, wrapping the individual argument patterns.
Stop using macro_escape as an inner attribute2015-01-05T20:00:57+00:00Keegan McAllisterkmcallister@mozilla.com2014-12-19T04:09:57+00:00urn:sha1:fc584793237c388e9dca76ef406d1af34e453fe2
In preparation for the rename.
std: Stabilize the prelude module2015-01-02T16:54:06+00:00Alex Crichtonalex@alexcrichton.com2014-12-22T17:04:23+00:00urn:sha1:56290a004493a5d2e211f056601533253497df60
This commit is an implementation of [RFC 503][rfc] which is a stabilization
story for the prelude. Most of the RFC was directly applied, removing reexports.
Some reexports are kept around, however:
* `range` remains until range syntax has landed to reduce churn.
* `Path` and `GenericPath` remain until path reform lands. This is done to
prevent many imports of `GenericPath` which will soon be removed.
* All `io` traits remain until I/O reform lands so imports can be rewritten all
at once to `std::io::prelude::*`.
This is a breaking change because many prelude reexports have been removed, and
the RFC can be consulted for the exact list of removed reexports, as well as to
find the locations of where to import them.
[rfc]: https://github.com/rust-lang/rfcs/blob/master/text/0503-prelude-stabilization.md
[breaking-change]
Closes #20068
librustc: Always parse `macro!()`/`macro![]` as expressions if not2014-12-18T17:09:07+00:00Patrick Waltonpcwalton@mimiga.net2014-11-14T17:18:10+00:00urn:sha1:ddb2466f6a1bb66f22824334022a4cee61c73bdc
followed by a semicolon.
This allows code like `vec![1i, 2, 3].len();` to work.
This breaks code that uses macros as statements without putting
semicolons after them, such as:
fn main() {
...
assert!(a == b)
assert!(c == d)
println(...);
}
It also breaks code that uses macros as items without semicolons:
local_data_key!(foo)
fn main() {
println("hello world")
}
Add semicolons to fix this code. Those two examples can be fixed as
follows:
fn main() {
...
assert!(a == b);
assert!(c == d);
println(...);
}
local_data_key!(foo);
fn main() {
println("hello world")
}
RFC #378.
Closes #18635.
[breaking-change]