3 ms·
I have! And I will... I just haven't gotten around to it yet. The main takeaway is specific to my use-case: writing a dynamic library that can be called from w
by crux 10y ago
I have! And I will... I just haven't gotten around to it yet.
The main takeaway is specific to my use-case: writing a dynamic library that can be called from within Python code. The main positive and negative are two sides of the same coin: since Nim compiles to C, you get to use all the existing tools designed for doing C FFI in Python, and don't have to write any C wrappers. And since Nim isn't C, there's still a little bit of detective work involved in replicating all the argument types, GC behavior, etc, that is involved in Nim and the specifics of its realization in C.
- emsy 10y agoHave you encountered any major compiler bugs? Nim looks great, but the list of open issues on GitHub would scare me from using it in production. Or isn't it as severe in real-world use?
- audunw 10y agoemsy: I'm not OP, but I encountered quite a few compiler bugs when I was using Nim a couple of years ago, but that was only because I tried to push the macro system really hard. Generally most bugs are related to newer features. I never experienced any bugs with the core features/library.
- zielmicha 10y agoThere are compiler bugs, but almost all of them are related to advanced metaprogramming. If you stick to "normal" metaprogramming (generics, templates, sane macros), compiler works well.
- crux 10y agoI haven't encountered any compiler bugs, no. I know that they're still really pushing on some of the further reaches—what comes to mind is statically verifying that a value is never `nil`, as well as some of the more industrial-strength elements of the metaprogramming system—but both of those are very much optional.
- deleted 10y ago[deleted]