rust/src/libsyntax/parse, branch 1.0.0-alpha.2 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.0.0-alpha.2 2015-02-19T00:34:04+00:00 Round 3 test fixes and conflicts 2015-02-19T00:34:04+00:00 Alex Crichton alex@alexcrichton.com 2015-02-18T23:58:07+00:00 urn:sha1:d6e939a2df16338e9cf63ad19d1025a15069387c rollup merge of #22502: nikomatsakis/deprecate-bracket-bracket 2015-02-18T23:48:40+00:00 Alex Crichton alex@alexcrichton.com 2015-02-18T23:48:40+00:00 urn:sha1:231eeaa35b3a7700cfd05dcb30f01cd7a36313b8 Conflicts: src/libcollections/slice.rs src/libcollections/str.rs src/librustc/middle/lang_items.rs src/librustc_back/rpath.rs src/librustc_typeck/check/regionck.rs src/libstd/ffi/os_str.rs src/libsyntax/diagnostic.rs src/libsyntax/parse/parser.rs src/libsyntax/util/interner.rs src/test/run-pass/regions-refcell.rs Replace all uses of `&foo[]` with `&foo[..]` en masse. 2015-02-18T22:36:03+00:00 Niko Matsakis niko@alum.mit.edu 2015-02-18T19:48:57+00:00 urn:sha1:9ea84aeed4ed3006eddb6a7b24e9714f2844cd22 Declare `&foo[]` to be obsolete syntax. Modify the obsolete mechanism to 2015-02-18T22:35:50+00:00 Niko Matsakis niko@alum.mit.edu 2015-02-18T19:47:14+00:00 urn:sha1:64cd30e0cacb6b509f9368004afb0b6bde7a5143 support warnings. rollup merge of #22497: nikomatsakis/suffixes 2015-02-18T22:35:01+00:00 Alex Crichton alex@alexcrichton.com 2015-02-18T22:35:01+00:00 urn:sha1:5250a82f7917d6f9ec590e7e762bfd036e21ef74 Conflicts: src/librustc_trans/trans/tvec.rs For now, accept the `i`, `u`, `is`, and `us` suffixes, but warn when 2015-02-18T20:08:40+00:00 Niko Matsakis niko@alum.mit.edu 2015-02-18T19:13:38+00:00 urn:sha1:811c48fe22ffbe4ca45c32807c846d9a7c02a8f3 they are used without a feature-gate. This is both kinder to existing code and should make it easier to land this PR, since we don't have to catch EVERY SINGLE SUFFIX. Modify parser to require `isize`/`usize` suffixes. 2015-02-18T14:07:56+00:00 Niko Matsakis niko@alum.mit.edu 2015-02-17T14:45:58+00:00 urn:sha1:700c518f2afd4b759fb54b867aee62660188d870 Remove usage of .map(|&foo| foo) 2015-02-18T00:57:35+00:00 Kevin Butler haqkrs@gmail.com 2015-02-15T05:19:50+00:00 urn:sha1:061206b9c75cf89b94dac1a2f358a0c649d796ae Opt for .cloned() over .map(|x| x.clone()) etc. 2015-02-18T00:56:07+00:00 Kevin Butler haqkrs@gmail.com 2015-02-13T07:33:44+00:00 urn:sha1:2f586b9687e5c33d9d3b8eccfc309f65d2a9f4e9 Rollup merge of #22285 - kmcallister:pub-macro, r=nick29581 2015-02-15T13:12:48+00:00 Manish Goregaokar manishsmail@gmail.com 2015-02-15T13:06:20+00:00 urn:sha1:16b24f15bd042c4f97e1d4826d82c992c0228684 It's not clear what this means, because a macro in item position can expand to zero or more items. For now we disallow it, which is technically a [breaking-change] but is landing without an RFC. The `pub` keyword previously had no effect, which seems quite unintended. Fixes #18317. Fixes #14660.