-
-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use moved core.lifetime.move{,Emplace} for std.algorithm.mutation.move{,Emplace} #6848
base: master
Are you sure you want to change the base?
Conversation
Thanks for your pull request, @wilzbach! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub fetch digger
dub run digger -- build "master + phobos#6848" |
assertThrown!Error(move(p)); | ||
assertThrown!Error(move(p, pp)); | ||
assertThrown!Error(swap(p, pp)); | ||
//import std.exception : assertThrown; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not delete instead of commenting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to see whether this is the only issue.
As explained, the core.lifetime functions are technically different and using them is a breaking change.
@thewilsonator this one is for you. |
In dlang/druntime#2442,
doesPointTo
wasn't ported as it's quite big (dlang/druntime#2447).That's why one test which test this behavior would fail now. Should we simply move
doesPointTo
to druntime as proposed, s.t. we don't need to maintain two implementations?