-
-
Notifications
You must be signed in to change notification settings - Fork 705
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
Fix issue 13930, 19345 - Fix receiveOnly for non-assignable types
#7655
Conversation
|
Thanks for your pull request and interest in making D better, @tom-tan! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please see CONTRIBUTING.md for more information. If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment. Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + phobos#7655" |
|
please rewrite the commit message to say |
4d7fc1e
to
d86c1f6
Compare
|
@thewilsonator Thank you for your advice. I updated the commit message. |
receiveOnly for non-assignable types (issue 13930, issue 19345)receiveOnly for non-assignable types
|
Thanks! |
|
This fails on Win32: I have no idea why it doesn't fail on other platform, but this needs to be reverted. I'm also going to set Azure as required so that the bot doesn't merge failing PRs. Sorry @tom-tan , could you re-submit a PR after the revert ? |
This request fixes the following two issues:
I used a different issue title for this request from the above two issues because the source of the problem is about
receiveOnlyrather thansendfunction orstd.concurrencyitself.