https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.37.0 2019-06-22T23:30:41+00:00 2019-06-22T23:30:41+00:00 Julien Cretin cretin@google.com 2019-05-29T18:05:43+00:00 urn:sha1:b8106b59d2faaea57301ad000d7787b70c5b2985 The errors are either: - The meta-variable used in the right-hand side is not bound (or defined) in the left-hand side. - The meta-variable used in the right-hand side does not repeat with the same kleene operator as its binder in the left-hand side. Either it does not repeat enough, or it uses a different operator somewhere. This change should have no semantic impact. 2019-04-09T18:05:15+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2019-04-09T18:04:21+00:00 urn:sha1:6688b03865ed727fb71c2f14bca02dfb403eba1f 2019-04-05T21:51:07+00:00 Josh Stone jistone@redhat.com 2019-04-05T21:51:07+00:00 urn:sha1:0730a01c5ca3b0e8760d72a05c47d4199bd64728 This updates the `Extend` implementations to use `for_each` for many collections: `BinaryHeap`, `BTreeMap`, `BTreeSet`, `LinkedList`, `Path`, `TokenStream`, `VecDeque`, and `Wtf8Buf`. Folding with `for_each` enables better performance than a `for`-loop for some iterators, especially if they can just forward to internal iterators, like `Chain` and `FlatMap` do. 2019-03-27T08:58:40+00:00 bors bors@rust-lang.org 2019-03-27T08:58:40+00:00 urn:sha1:c5fb4d0d2f464bc9ab61f7693ed4dde4d9326820 Introduce proc_macro::Span::source_text A function to extract the actual source behind a Span. Background: I would like to use `syn` in a `build.rs` script to parse the rust code, and extract part of the source code. However, `syn` only gives access to proc_macro2::Span, and i would like to get the source code behind that. I opened an issue on proc_macro2 bug tracker for this feature https://github.com/alexcrichton/proc-macro2/issues/110 and @alexcrichton said the feature should first go upstream in proc_macro. So there it is! Since most of the Span API is unstable anyway, this is guarded by the same `proc_macro_span` feature as everything else. 2019-02-24T12:59:44+00:00 Taiki Endo te316e89@gmail.com 2019-02-24T12:59:44+00:00 urn:sha1:871910a2c6e8624d4ebaa08ce6201b661f8c25f3 2019-02-14T01:41:16+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-02-14T01:41:16+00:00 urn:sha1:aa896f30bb7f848b8becf54b614b8eadcef22a26 Convert old first edition links to current edition one r? @steveklabnik 2019-02-13T14:39:25+00:00 Lzu Tao taolzu@gmail.com 2019-01-23T03:55:37+00:00 urn:sha1:e7f8e63ed425cef77a9ad43e463b39009c1a495a Use footnote style to bypass the tidy check 2019-02-12T19:09:24+00:00 bors bors@rust-lang.org 2019-02-12T19:09:24+00:00 urn:sha1:b244f61b77c42d7be695afd7901ee4418559e518 Cosmetic improvements to doc comments This has been factored out from https://github.com/rust-lang/rust/pull/58036 to only include changes to documentation comments (throughout the rustc codebase). r? @steveklabnik Once you're happy with this, maybe we could get it through with r=1, so it doesn't constantly get invalidated? (I'm not sure this will be an issue, but just in case...) Anyway, thanks for your advice so far! 2019-02-10T23:42:32+00:00 Alexander Regueiro alexreg@me.com 2019-02-09T21:23:30+00:00 urn:sha1:b87363e7632b3f20f9b529696ffb5d5d9c3927cd 2019-02-10T07:13:30+00:00 Taiki Endo te316e89@gmail.com 2019-02-10T07:13:30+00:00 urn:sha1:2be0993c4e219994b355a06e82394c966a2cfa5d