3 ms·
I have love-hate relationship with Nim. It's the best C alternative I can find for our high performance supercomputing needs, yet it breaks my code [0] (yes, i
by jxy 10y ago
I have love-hate relationship with Nim. It's the best C alternative I can find for our high performance supercomputing needs, yet it breaks my code [0] (yes, it's broken with 0.16.0 now) every single new release for the past year.
[0] https://github.com/jxy/tpl https://github.com/jxy/tpl
- dom96 10y agoSorry about that. Have the changes which break your code been documented in the changelog? If not please report them[0], if this is a regression then it should be fixed quickly. 0 - https://github.com/nim-lang/Nim/issues/new https://github.com/nim-lang/Nim/issues/new
- jxy 10y agoIt's a problem with macro heavy code in Nim currently. Macros on typed NimNode still touch too many undocumented/unspecified Nim internals, that it always takes me some time to actually figure out what is the culprit. On the other hand, code without much typed macro transformations is really solid now, c.f. [0], the repo you are watching. [0] https://github.com/jcosborn/qex https://github.com/jcosborn/qex
- dom96 10y agoI see. I would guess that macros on typed NimNodes are indeed unstable and underused :\ Please don't give up on us. I see that you've already created a couple of issues, if we forget about them then please keep pinging us on GitHub or IRC.