Closed gnzlbg closed 6 years ago
So the last commit without breaking changes was: https://github.com/fitzgen/mach/commit/592d9e995f46195f2b87bdeae3c316e125f7db2a and that should be published as mach 0.1.3. All commits after that one have ABI fixes and should be published as 0.2.0.
This doesn't appear to have been required, we can do it if somebody requests this. In the mean time, I hope everybody upgraded to 0.2 and that the update went smoothly (that is, that they weren't using any of the ABIs that were not matching the C ones).
Fixing any ABI issues like the ones shown in #20 is going to break the library API. I think it makes sense to do a minor release before starting to fix them, and then do a major release when they are fixed.