-
Notifications
You must be signed in to change notification settings - Fork 6
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
Move to GitHub merge queues. #228
Conversation
This setting causes problems and we don't gain sufficient benefit from it.
Any squashing to be done? |
I think the two commits should be separate. |
@vext01 This one should be ready to re-review and merge. |
I think @ltratt is better qualified for yksom changes. |
Sure, but I think you'll need to do the final sign off because Laurie opened the PR. |
Yes, @vext01 you need to review this please. |
@@ -79,6 +79,8 @@ pub struct Block { | |||
// this explicit impl is needed to tell the compiler we are not doing that. | |||
unsafe impl FinalizerSafe for Block {} | |||
|
|||
unsafe impl Sync for Block {} |
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.
Do you need a comment saying why this is safe?
Bearing in mind I don't know much about the GC :)
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.
Sure! I've documented it here: e43d305
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.
Sorry, I meant for the various unsafe impl Sync for Blah {}
s.
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.
AFAICS all of them are now documented.
Please squash. |
This is needed because their trait objects are passed to a GC so must be FSA-safe.
e43d305
to
676db21
Compare
Squashed |
Ok so when softdevteam/alloy#101 lands, this should be merge-able :) |
sorry, i didn't see it had failed. |
It's a rustfmt problem. I've fixed it here: 9aa838, let me know if I can squash. |
Go ahead. |
9aa838a
to
4b540c3
Compare
Squashed |
Did you forget to sign the commit? |
Weird! My gpg-agent has failed. Can I force-push an update? |
Please push a signed commit. |
The SmartString library uses pointer obfuscation tricks internally which hide GC pointers from alloy. We must therefore remove it as it is incompatible with conservative pointer scanning.
4b540c3
to
0e4445f
Compare
Force-pushed a signed commit. |
Ugh I’ve not seen that one before. |
ouch. |
Any news on this one? |
That's one for @jacob-hughes. |
@vext01 You should be able to merge this one now :) |
No description provided.