Matheus C. França

>Hmm, testing on my M1 Mac with ldc2 I'm seeing a couple of weird issues: > >Warnings like this: What flags were used? I tested only on linux and windows...

> Hmm, I was just running `zig build clear` etc... and then started `zig-out/bin/clear`. After some changes to `build.zig`, to build and run are similar to sokol-zig. https://github.com/kassane/sokol-d/commit/ad3ca49daba6fdbd410ca055237247ecb560839d > If...

> Remove helper code (by @ryuukk) There will be no more auto-generation of helper functions. Providing these conversions will be the responsibility of the user. It may also be possible...

Now, solved NaN init issues! (debugtext_print and sgl_context fixed) But, need fix shaders in pipeline objects conflicts!

Finally CI (gen d binding added) :heavy_check_mark:

For initial support, this solution already works. Waiting for your review! cc: @floooh -- Edit Any corrections and improvements will be handled by sokol-d directly, since I haven't yet identified...

Currently I use lldb extension to debug in vscode. For `scope` issue, I also suggest trying to remove the `-preview=all` dflag (experimental features - including DIP1000 that makes `@safe`/`scope` more...

> ...on Ubuntu with ldc2 version 1.30.0, if I remove the `scope` attribute from functions, the samples compile (with a couple of warnings about GC and thread-local variables), but there...

> ...the warning 'apple_a14' is not a recognized processor for this target (ignoring processor) seems to be triggered by the code which sets the target triple and processor (I just...

> The `sg.Range` helper seems to be broken, it returns a `.size` of 8 (the size of a pointer) instead of the size of the array data, I guess because...