glam => 0.27 #726
Merged
glam => 0.27 #726
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! Pretty sure the issues are not glam related! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates
glamto version0.27.My main motivation here is to at least hit
0.24for the convenience of thesaturating_*functions on the integer vector types.I get a few unrelated test failures locally so I can't 100% verify that this is ok, but output is at least identical to running tests on
masterwhich is promising. For completeness, the failures are the coroutine tests as noted at #693, and a number of doc tests. Running anything locally with this build hasn't caused me any problems on either MacOS or Linux X11.