You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I greatly appreciate the work you did to make naming clearer and more consistent than the Intel intrinsics. That being said, there's still a bit of work to do to perfect this, particularly around shuffles and permute. However, that would be an API-breaking change by definition.
How would you feel about a patch for this ? Break API and bump semver release number, or keep the existing methods as deprecated with new aliases following the convention ?
The text was updated successfully, but these errors were encountered:
Having a 0.6.1 that just does the deprecating is probably better, and then if a 0.7 is released for some other reason we could remove the old names entirely.
I greatly appreciate the work you did to make naming clearer and more consistent than the Intel intrinsics. That being said, there's still a bit of work to do to perfect this, particularly around shuffles and permute. However, that would be an API-breaking change by definition.
How would you feel about a patch for this ? Break API and bump semver release number, or keep the existing methods as deprecated with new aliases following the convention ?
The text was updated successfully, but these errors were encountered: