Uh oh!
There was an error while loading. Please reload this page.
Allow ZSTs in AllocRef - #69799
Conversation
rust-highfive
commented
Mar 7, 2020
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
rust-highfive
commented
Mar 7, 2020
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
rust-highfive
commented
Mar 7, 2020
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Do we want requirements for Currently, it's unspecified. |
Amanieu
commented
Mar 8, 2020
Let's defer the @bors r+ rollup=always |
bors
commented
Mar 8, 2020
📌 Commit f77afc8 has been approved by |
bors
commented
Mar 8, 2020
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
Centril
commented
Mar 9, 2020
I don't think this is risk free enough to rollup=always; @bors rollup=maybe |
Allow ZSTs in `AllocRef` Allows ZSTs in all `AllocRef` methods. The implementation of `AllocRef` for `Global` and `System` were adjusted to reflect those changes. This is the second item on the roadmap to support ZSTs in `AllocRef`: rust-lang/wg-allocators#38 (comment) After this has landed, I will adapt `RawVec`, but since this will be a pretty big overhaul, it makes sense to do a different PR for it. ~~Requires rust-lang#69794 to land first~~ r? @Amanieu
Rollup of 6 pull requests Successful merges: - #69475 (Remove the `no_force` query attribute) - #69514 (Remove spotlight) - #69677 (rustc_metadata: Give decoder access to whole crate store) - #69714 (Make PlaceRef take just one lifetime) - #69799 (Allow ZSTs in `AllocRef`) - #69836 (Check if output is immediate value) Failed merges: r? @ghost
Rollup of 10 pull requests Successful merges: - #69475 (Remove the `no_force` query attribute) - #69514 (Remove spotlight) - #69677 (rustc_metadata: Give decoder access to whole crate store) - #69714 (Make PlaceRef take just one lifetime) - #69799 (Allow ZSTs in `AllocRef`) - #69817 (test(patterns): add patterns feature tests to borrowck test suite) - #69836 (Check if output is immediate value) - #69847 (clean up E0393 explanation) - #69861 (Add note about localization to std::fmt docs) - #69877 (Vec::new is const stable in 1.39 not 1.32) Failed merges: r? @ghost
Allows ZSTs in all
AllocRefmethods. The implementation ofAllocRefforGlobalandSystemwere adjusted to reflect those changes.This is the second item on the roadmap to support ZSTs in
AllocRef: rust-lang/wg-allocators#38 (comment)After this has landed, I will adapt
RawVec, but since this will be a pretty big overhaul, it makes sense to do a different PR for it.Requires #69794 to land firstr? @Amanieu