https://nim-lang.org/blog/2023/08/01/nim-v20-released.html
Well, what can I say... It took longer than expected. With ensureMove and =dup and =wasMoved and the non-var-T destructors and refinements regarding Isolated[T] the ORC model is finally complete.
Next step is to update the book to mention these more recent developments. I will add a chapter about multi-threading and Nim's new memory model. This time the book will have an E-book version so that you all can buy it a 2nd time.
A big thanks to everybody who contributed!
Now here is some questions&answers:
Q: What about IC? A: Bugs aside, the way we implemented IC doesn't show enough of a performance benefit so we'll redo the way it works yet again. Sorry.
Q: What is your favorite feature of this release? A: Overloadable enums.
Q: This version has been in development for good, why release it today? A: Because I need some vacation and it's mean to deprive people of all the progress we have been able to achieve.
Congrats! š
Have a great well-deserved vacation Andreas!
Huge thanks to everyone in the Nim core team and all the package maintainers for your work š
Congratulations! There is a lot to love about this new release. Iām particularly happy that ORC has finally become the default memory management strategy.
@Araq, since you mention it in your post, what is the new approach for IC?
Anyway, enjoy your well deserved vacation. Thanks a lot for your hard work!
since you mention it in your post, what is the new approach for IC?
Compiling modules into some interface file that loses information (!) so that the serialization steps finally become cheap enough.
Scala - incoherent mess.
LOL! I dabbled in Scala at caesars, i hated it, everyone fkn hated it. But I did grow as a programmer learning it