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
Thanks, that's a good idea. I hesitated because I didn't make functional changes since v1.5.0. But it looks like I did a lot of work since then. Upon reviewing my series of commits, these are the main things I did:
Clarified a lot of internal code (especially for Rust, C++, and C).
Merged the C++ source files from 3 pairs to just 1 pair.
Modified internal assertions (which should not trigger unless I made a mistake).
Deleted JavaScript in favor of TypeScript.
Made very minimal changes to Java and Python source codes.
Given the same inputs, the libraries as of latest (commit 13a2558) still generate the exact same output as v1.5.0. Also, I keep master stable, so any project that took a non-tagged commit from my project is okay and not risky.
I think that it would be good to flush currently committed changes and make new release :)
Looks like already at least few distributions are no longer using regular 1.5.0.
The text was updated successfully, but these errors were encountered: