-
Notifications
You must be signed in to change notification settings - Fork 184
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
Fallback-aware datagen #3487
Fallback-aware datagen #3487
Conversation
3debcf6
to
b800f38
Compare
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.
Still not sure about the "batteries included" approach to fallback, but this is close to how I think the code should look if we were to take that approach
f4c924c
to
79392e4
Compare
The batteries included discussion is isolated in |
Removed the |
@@ -53,7 +53,7 @@ impl core::fmt::Debug for ExportBox { | |||
impl<M> UpcastDataPayload<M> for ExportMarker | |||
where | |||
M: DataMarker, | |||
M::Yokeable: Sync, | |||
M::Yokeable: Sync + Send, |
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.
This is technically breaking, but I think it's almost impossible to have !Send
data structs, as they'd have to contain raw pointers or Rc
. If we don't want this we can remove locale-level parallelism and generate all locales for each key on the same thread.
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 lean toward shipping this and rolling back if anyone has problems
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.
LGTM with open questions regarding the exact behavior of the fallback modes
Part of #2683
Needed for builtin data.