Jason Beetham
Jason Beetham
As nice as genny is I think something akin to cbindgen or nbindgen makes a bit more sense, especially since the Nim compiler can be used mostly as a library....
The present object constructor syntax(aside from not inferring generics) is fine, if you something more sweet you can easily write your own or use a package(as disruptek alluded to). As...
On planetis' request I'll document a possible solution to this problem: ```nim import std/typetraits type AtomicBases = concept a, type A distinctBase(A) is AtomType AllAtomTypes = AtomType or AtomicBases Atomic*[T:...
This seems to just be a workaround version of "Object constructors should infer the type". There is no reason one needs to specify default specialization if the following is valid....
Well I thought this was going to be a few sentences but I have written a bit more. > This feature would still be useful to save some typing in...
Does it work if you have the `config.nims`?
Well well well 1 step forward 2 steps back... where are your compiler sources located?
Hmph, the only issue is that the fix is not back-ported, so I guess to support 1.6.x I still need that import hack I mentioned.
https://github.com/beef331/nimscripter/blob/master/src/nimscripter.nim#L87-L90 Need a version that takes in a `openarray[(string, VMAddins)]` or similar and implements each per string.
I have hooked up a CI for docgen(begrudgingly :stuck_out_tongue: )