Plans for CIVersioning
Number: X.Y.Z
CI will automatically handle versioning, committing it directly to the main branch as part of the automated release pipeline ("Tuesday Snap"). For Patch Tuesday, it sets Z to zero and increments Y; X remains unchanged. For emergency patches, only Z is incremented, leaving the others untouched. The version is automatically incremented, pushed to main by CI, and then tagged and released....
also I think the whole "oh look how cool on browser (on other platforms go fuck yourself) you can just include your C file and then do DllImport with the C files name" thing is just a lie
Sorry, got caught up in a big mess at the end of the week, so everything got halted. I am going to get back into it hopefully today or tomorrow. I have updated the proposals, with the Any overloads idea (which allows you to use the unmanaged and managed chaining systems with 'looser' constraints when you want to), and it works well. I also implement equality on ManagedChain to make them more similar to Tuple. However, I have encountered the wierdest bug ever in my GetHashCode impleme...
