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 am wondering how everyone feels about doing a version bump on UInt128? If we were to do one, does everyone feel that it is ready for a 1.0.0 release? I'm also not up to date on Swift packaging. If I were to just push a tag for a new release, would that be enough for all of the cool package managers to find it, or should something else happen?
For a v1.0, I have a large update in the works adding StaticBigInt support requiring Swift 5.8, also adding AdditiveArithmetic, Sendable, CustomPlaygroundDisplayConvertible.
Interesting. Feel free to break it up into bits if you'd like. I'll want to understand what risks and rewards come with the new functionality and changes. If they make sense and keep the library lightweight, I'd be happy to merge them and cut a 1.0 release.
I am wondering how everyone feels about doing a version bump on UInt128? If we were to do one, does everyone feel that it is ready for a 1.0.0 release? I'm also not up to date on Swift packaging. If I were to just push a tag for a new release, would that be enough for all of the cool package managers to find it, or should something else happen?
@gongzhang & @adamnemecek; I'm especially interested to hear your thoughts on this.
The text was updated successfully, but these errors were encountered: