Prepare v0.4.1 release#210
Merged
Merged
Conversation
Shnatsel
approved these changes
May 16, 2026
Contributor
Shnatsel
left a comment
There was a problem hiding this comment.
One broken link, otherwise LGTM.
FYI you can use [foo] instead of [foo][] syntax, which is less verbose.
Collaborator
Author
I'm also not sure why we do this but I believe there is a reason, it's also done in the other repos. Therefore, I'll leave it as is for now. |
Member
|
We use In particular, that's useful because forgetting to add links is really easy. |
This file contains hidden or 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
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.
#208 is not breaking because the restrictions already existed, we just forgot to add them everywhere.
I realized that in theory #207 would be breaking because while the
Simdtrait requiresSeal,SimdIntandSimdBasecurrently do not, I think that's an oversight. However, those traits are not intended to be implemented manually anyway, so let's just fix that in a follow-up.