-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
[Merged by Bors] - Minimally fix the known unsoundness in bevy_mikktspace #5299
Conversation
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.
The existing code is not fun to navigate, but these changes make sense. I'd rather ship with these than nothing.
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.
These look simple enough to me. @cart please take a look.
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.
Looks good to me. Thanks for making this easy on us! I really like the "fully safe port" effort, but I was not looking forward to reviewing that under these time constraints :)
bors r+ |
# Objective - 0.8 is coming soon, and our mikktspace implementation is unsound - see gltf-rs/mikktspace#26 - Best not to ship that ## Solution - Fix the unsoundness in a minimal way - Obviously there might be others, but it seems unlikely we have any way to know about those
Build failed: |
bors retry |
# Objective - 0.8 is coming soon, and our mikktspace implementation is unsound - see gltf-rs/mikktspace#26 - Best not to ship that ## Solution - Fix the unsoundness in a minimal way - Obviously there might be others, but it seems unlikely we have any way to know about those
Build failed: |
bors retry |
# Objective - 0.8 is coming soon, and our mikktspace implementation is unsound - see gltf-rs/mikktspace#26 - Best not to ship that ## Solution - Fix the unsoundness in a minimal way - Obviously there might be others, but it seems unlikely we have any way to know about those
two previous CI failures are due to lack of disk space on windows |
Pull request successfully merged into main. Build succeeded: |
# Objective - 0.8 is coming soon, and our mikktspace implementation is unsound - see gltf-rs/mikktspace#26 - Best not to ship that ## Solution - Fix the unsoundness in a minimal way - Obviously there might be others, but it seems unlikely we have any way to know about those
# Objective - 0.8 is coming soon, and our mikktspace implementation is unsound - see gltf-rs/mikktspace#26 - Best not to ship that ## Solution - Fix the unsoundness in a minimal way - Obviously there might be others, but it seems unlikely we have any way to know about those
# Objective - 0.8 is coming soon, and our mikktspace implementation is unsound - see gltf-rs/mikktspace#26 - Best not to ship that ## Solution - Fix the unsoundness in a minimal way - Obviously there might be others, but it seems unlikely we have any way to know about those
Objective
Solution