Dmitry Matveyev

> It totally went over my head that `` `[]`, `[]=` `` both suffer from [nim-lang/Nim#19351](https://github.com/nim-lang/Nim/issues/19351) We need `.copy` pragma for procs as araq suggested. Does `.copy` pragma imply that...

There's an example of using a C callback function from Nim, does it help? https://github.com/greenfork/nimraylib_now/blob/master/examples/core/core_custom_logging.nim

There's still `va_list` type from C varargs. I'm not sure that we want it because if we choose to change it, we make it Nim-native implementation. Here we still have...

@planetis-m what is our current state of JSON vs c2nim implementation, what are your thoughts? JSON still has some problems as c2nim at least with pointers/arrays. So it's not that...

I see! Okay, than I will do my part at restructuring the pipeline and I will take a closer look at how to integrate all the great stuff in the...

That is a lot of input from your side, thank you! I will take a look at it

Could you please try this: ```nim import nimraylib_now/raylib import nimraylib_now/physac proc test*()= discard RayWhite initPhysics() let body = createPhysicsBodyRectangle((0.0, 0.0), 32.0, 32.0, 10.0) ``` Here we add `discard RayWhite` so...

This looks like the issue is with the order of imports: ```c // /home/grfork/.cache/nim/main_d/@[email protected] /* Generated by Nim Compiler v1.4.4 */ /* (c) 2020 Andreas Rumpf */ /* The generated...

One of the solutions to this problem is to create a single header file out of all other headers. This way we control the order of imports.

This looks a bit dense and it uses a peg-like syntax instead of familiar regex but I think it should be fairly understandable. Let's wait until your c2nim PR is...