Timothee Cour

in the meantime https://github.com/PMunch/protobuf-nim/issues/12 would mitigate this

you gave wrong link in https://github.com/PMunch/protobuf-nim/issues/10#issuecomment-378174379 , shd be https://github.com/nim-lang/Nim/pull/7481

thanks for all the answers! > I remember issues with generic converters... - [ ] I think this was fixed https://github.com/nim-lang/Nim/issues/8403 ; what other issues do you have in mind?...

@dom96 do you mind adding me as contributor so I can add label "low priority"? (that's what I had done in original https://github.com/nim-lang/Nim/issues/10163, which I had wrongly posted to wrong...

we should close this now that https://github.com/cheatfate/asynctools/pull/19 was merged

@carun added a caveat in https://github.com/timotheecour/D_vs_nim/commit/e06274414fc71df6dad5aa2c99566c04dd596694 Adding a dummy argument is the common workaround for lack of default struct constructors: ```d struct A{ T data; this(int dummy){ // initialize data...

comment from @Laeeth which I'm moving to here: > I guess you should mention extern(C++). You can use dpp to #include C++ headers if you blacklist STL and Boost types...

PR's welcome to update this section (especially with the latest D work on `extern(C++)`, but it deserves a whole entry on its own; this is something I've been very interested...

* [[Grant Proposal] Make Nim suitable for interactive programming (Implement hot code-reloading, a REPL and a Jupyter kernel) · Issue nim-lang/RFCs#511 · nim-lang/Nim](https://github.com/nim-lang/RFCs/issues/511)

PRs welcome to update the info in this repo! as you can see here https://github.com/timotheecour/D_vs_nim/pulls?q=is%3Apr+is%3Aclosed I usually merge them pretty fast