-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add opt-out fragile-send-sync-non-atomic-wasm
feature for wgpu
#5098
Conversation
…mics on wasm with egui and wgpu.
c3ea6ae
to
2d0c1cf
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.
good to go after ci version pin
fragile-send-sync-non-atomic-wasm
feature for wgpu
Co-authored-by: Andreas Reich <[email protected]>
@Wumpf done. Thanks for catching the somewhat embarrassing oversight in the actual source code ;-P. |
Thanks for taking the time @Wumpf! |
@emilk this was in the release yesterday, was it not? Just asking because I would like to remove my patch to the master branch, this is a bit annoying. When I checked the changelog it wasn't mentioned, but when I look at the respective git tag it seems to be present. |
it's part of the release 👍 |
…lk#5098) Note this will break people depending on eframe or egui-wgpu with --no-default-features. I don't know what to do about that to be honest. * Closes emilk#4914 * [x] I have followed the instructions in the PR template --------- Co-authored-by: Andreas Reich <[email protected]>
Note this will break people depending on eframe or egui-wgpu with --no-default-features.
I don't know what to do about that to be honest.