Uh oh!
There was an error while loading. Please reload this page.
[RFC] Entry API v3: replace Entry::get with Entry::default and Entry::default_with - #22930
Conversation
rust-highfive
commented
Mar 1, 2015
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
d7782ad to
009f861CompareGankra
commented
Mar 2, 2015
RFC posted: rust-lang/rfcs#921 All imports/typos/missed-things fixed. |
bors
commented
Mar 7, 2015
☔ The latest upstream changes (presumably #23107) made this pull request unmergeable. Please resolve the merge conflicts. |
aturon
commented
Mar 19, 2015
Note: the RFC has now been merged (with updated names) |
c9b5258 to
0c4a120CompareGankra
commented
Mar 20, 2015
Rebased with updated names. r? @aturon |
alexcrichton
commented
Mar 20, 2015
(added I'd also be fine insta-stabilizing these methods as they've been around for quite some time and we're just tweaking the naming here basically. |
Gankra
commented
Mar 20, 2015
I'm not comfortable stabilizing these quite yet. We could go one step further and just make these methods on the Map itself, for instance. I also see no particular urgency to stabilize them; they are pure convenience (though very convenient indeed). |
Gankra
commented
Mar 20, 2015
Oh whoops I forgot to actually, you know, test the rebase/fix. Tidy error fixed; building now. |
aturon
commented
Mar 20, 2015
This is really, really nice! You've done great work with I also agree that there's no rush to stabilize these new methods, which are more than a rename. |
aturon
commented
Mar 20, 2015
r=me once tests are looking good locally |
Gankra
commented
Mar 20, 2015
looks good locally (had to make one update) |
aturon
commented
Mar 23, 2015
(r=me after nits) |
bors
commented
Mar 23, 2015
☔ The latest upstream changes (presumably #23593) made this pull request unmergeable. Please resolve the merge conflicts. |
aturon
commented
Mar 23, 2015
Given the proximity to beta, I'm thinking we should probably go ahead and mark these Worst case, if we do find a problem, we can revise before 1.0. |
Gankra
commented
Mar 24, 2015
I'd really like to let this sit if possible. Although empirically it seems like we've played very fast and loose with stable vs unstable so far. Is it possible to stabilize things in the beta -> stable transition? There's still (in my mind) open questions about whether this functionality should just be on the map directly. Although I suppose we can deprecate this in favour of that quite easily. |
aturon
commented
Mar 24, 2015
@gankro I'm happy to defer to your judgment here. In terms of ongoing stabilization: we will be adding unstable APIs, and stabilizing existing ones, continuously. It is likely possible to stabilize a few APIs during the 1.0 beta and have those available at 1.0, but it's not entirely clear yet. In terms of "fast and loose", I'm not sure exactly what you're referring to -- perhaps just that we've been willing to change |
Gankra
commented
Mar 24, 2015
Easy to stabilize later; let's land this unstable for now. Can review in coming weeks, perhaps with removal of deprecated API. |
Gankra
commented
Mar 24, 2015
@bors r=aturon |
bors
commented
Mar 24, 2015
📌 Commit d3d11b2 has been approved by |
bors
commented
Mar 24, 2015
☔ The latest upstream changes (presumably #23654) made this pull request unmergeable. Please resolve the merge conflicts. |
Gankra
commented
Mar 27, 2015
Ugh what another rebase? |
Gankra
commented
Mar 27, 2015
@bors r=aturon |
bors
commented
Mar 27, 2015
📌 Commit 1132198 has been approved by |
RFC pending, but this is the patch that does it. Totally untested. Likely needs some removed imports. std::collections docs should also be updated to provide better examples. Closes#23508
bors
commented
Mar 27, 2015
bors
commented
Mar 27, 2015
💔 Test failed - auto-linux-64-x-android-t |
Gankra
commented
Mar 27, 2015
@bors r=aturon |
bors
commented
Mar 27, 2015
📌 Commit 1b98f6d has been approved by |
bors
commented
Mar 27, 2015
RFC pending, but this is the patch that does it. Totally untested. Likely needs some removed imports. std::collections docs should also be updated to provide better examples. Closes#23508
bors
commented
Mar 27, 2015
…c_on_a_qualified_path_whose_trait_is_not_a_trait fix: don't panic on a qualified path whose trait is not a trait
RFC pending, but this is the patch that does it.
Totally untested. Likely needs some removed imports. std::collections docs should also be updated to provide better examples.
Closes#23508