rust/src/librustc_codegen_ssa/mir, branch 1.34.2https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.34.22019-02-25T07:52:46+00:00librustc_codegen_ssa: deny(elided_lifetimes_in_paths)2019-02-25T07:52:46+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-02-25T07:52:46+00:00urn:sha1:1d34f2c22879886fcd452da096317861f8a0c9e6Reuse the `Pointer` type instead of passing reassembling it at many use sites2019-02-16T13:29:27+00:00Oliver Scherergithub35764891676564198441@oli-obk.de2019-02-16T13:29:27+00:00urn:sha1:f7c493121d4989895dd9c213ed4e877429229b86Auto merge of #58341 - alexreg:cosmetic-2-doc-comments, r=steveklabnik2019-02-12T19:09:24+00:00borsbors@rust-lang.org2019-02-12T19:09:24+00:00urn: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!
rustc: doc comments2019-02-10T23:42:32+00:00Alexander Regueiroalexreg@me.com2019-02-08T13:53:55+00:00urn:sha1:c3e182cf43aea2c010a1915eb37293a458df2228librustc_codegen_ssa => 20182019-02-09T14:31:47+00:00Taiki Endote316e89@gmail.com2019-02-09T14:31:47+00:00urn:sha1:be71fccf11525118b62b40f78c65b6bb6abca823Do not ICE in codegen given a extern_type static2019-02-05T21:20:07+00:00Dan Robertsondan@dlrobertson.com2019-02-05T15:52:54+00:00urn:sha1:80c052bed76d7b7406e956747012bc8a929fe909
The layout of a extern_type static is unsized, but may pass the
Well-Formed check in typeck. As a result, we cannot assume that
a static is sized when generating the `Place` for an r-value.
Auto merge of #55704 - Nemo157:pinned-generators, r=Zoxc2019-01-28T14:12:15+00:00borsbors@rust-lang.org2019-01-28T14:12:15+00:00urn:sha1:d8a0dd7ae88023bd09fa4b86c9ca1f6ed8095b43
Use pinning for generators to make trait safe
I'm unsure whether there needs to be any changes to the actual generator transform. Tests are passing so the fact that `Pin<&mut T>` is fundamentally the same as `&mut T` seems to allow it to still work, but maybe there's something subtle here that could go wrong.
This is specified in [RFC 2349 ยง Immovable generators](https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md#immovable-generators) (although, since that RFC it has become safe to create an immovable generator, and instead it's unsafe to resume any generator; with these changes both are now safe and instead the unsafety is moved to creating a `Pin<&mut [static generator]>` which there are safe APIs for).
CC #43122
Update generator upvar debug info2019-01-27T21:58:59+00:00Wim Loomanwim@nemo157.com2018-11-07T09:33:35+00:00urn:sha1:e7d66758cfce4dc2c87e3224b6ed47aee1fee257`ConstValue::ScalarPair` only needs to represent slices2019-01-27T20:41:35+00:00Oliver Scherergithub35764891676564198441@oli-obk.de2019-01-08T12:49:37+00:00urn:sha1:fe50b4eb1d6f7a31c53798bca3d0fa2b0670fa3dGet rid of the fake stack frame2019-01-22T16:22:29+00:00Oliver Scherergithub35764891676564198441@oli-obk.de2019-01-14T16:54:00+00:00urn:sha1:a59eabbc36d7b96bb9e42d9bc6691d28b62c4187