Uh oh!
There was an error while loading. Please reload this page.
[WIP] Commenting out unsound specialization. - #68280
Conversation
If perf results indicate that we need this, then we should try to emulate it via a series of implementations on concrete types.
rust-highfive
commented
Jan 16, 2020
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
pnkfelix
commented
Jan 16, 2020
@bors try |
rust-timer
commented
Jan 16, 2020
Awaiting bors try build completion |
bors
commented
Jan 16, 2020
⌛ Trying commit f2e1357 with merge 4b018ef117d5404402ea68ca020e5409a10695f6... |
rust-highfive
commented
Jan 16, 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 |
bors
commented
Jan 16, 2020
☀️ Try build successful - checks-azure |
rust-timer
commented
Jan 16, 2020
Queued 4b018ef117d5404402ea68ca020e5409a10695f6 with parent 9fe05e9, future comparison URL. |
rust-timer
commented
Jan 16, 2020
Finished benchmarking try commit 4b018ef117d5404402ea68ca020e5409a10695f6, comparison URL. |
nikomatsakis
commented
Jan 17, 2020
perf results look clean, at least, but maybe we should ping the original authors to see if they had particular cases in mind? I think @joshtriplett mentioned something about inclusive range performance being problematic, perhaps they remember. |
matthewjasper
commented
Jan 17, 2020
Test failure is legit. The specialization is being used for correct behaviour. I think that |
joshtriplett
commented
Jan 18, 2020
via email
On January 17, 2020 3:00:15 PM PST, Niko Matsakis ***@***.***> wrote:
perf results look clean, at least, but maybe we should ping the
original authors to see if they had particular cases in mind? I think
@joshtriplett mentioned something about inclusive range performance
being problematic, perhaps they remember. If the perf results look good, I have no objections. Might want to check with the authors though. |
nikomatsakis
commented
Jan 18, 2020
Eep! I didn't look that closely at the code... |
pnkfelix
commented
Jan 28, 2020
I'll try to look into this during whatever down-time I have today. |
I discussed this with @alexcrichton today. They said the libs team would take charge on how to handle this PR and issue #67194 |
pnkfelix
commented
Jan 30, 2020
(see also PR ##68358 ) |
pnkfelix
commented
Feb 10, 2020
We do not need this anymore; PR #68835 resolved the unsoundness in question (by changing the representation of |
If perf results indicate that we need this, then we should try to emulate it via a series of implementations on concrete types.
cc #67194