4 ms·

> V does seem to lean very heavily on inlined C inside its standard library and compiler. So that assessment is totally fair. If you don't mind me asking, how

> V does seem to lean very heavily on inlined C inside its standard library and compiler. So that assessment is totally fair. If you don't mind me asking, how heavily did Nim rely on inlined C inside it's standard library and compiler when it was only 3 months old? Or did you guys do something different that early in it's development?

dom96 7y ago
I wasn't around back then. But as far as I know there was never much inline C used, many C functions were wrapped sure, but that's necessary to use POSIX/WinAPIs. Nim has always had a "everything should be implemented in pure Nim" philosophy. So much so that the stdlib is even separated into "pure" modules[1] (implemented in Nim completely) and "impure" modules (those that depend on external C/C++ libs). Nowadays major things are implemented in Nim, for example we don't use libuv/libevent but instead have written our own epoll/kqueue/IOCP implementation. 1 - https://github.com/nim-lang/Nim/tree/devel/lib/pure https://github.com/nim-lang/Nim/tree/devel/lib/pure