raylib functions often take an array and it's length as arguments. This is fine in C, because it doesn't have a concept of "fat-pointers", or "slices", but on the Zig side we try to map these array/length pairs to slices wherever possible.
This affects all of the following:
[x] setWindowIcons
[x] saveFileData
[x] exportDataAsCode
[x] compressData
[x] decompressData
[x] encodeDataBase64
[x] loadImageFromMemory
[x] loadFontFromMemory
[x] loadFontData
[x] drawMeshInstanced
[x] unloadModelAnimations
[x] loadWaveFromMemory
[x] loadMusicStreamFromMemory
[ ] drawLineStrip
[ ] drawTriangleFan
[ ] drawTriangleStrip
[ ] checkCollisionPointPoly
[ ] loadFontEx
[ ] genImageFontAtlas
[ ] unloadFontData
[ ] drawTextCodepoints
[ ] loadUTF8
[ ] textJoin
[ ] drawTriangleStrip3D
However, I would like to postpone further fixes until Zig 0.11.0 is released and #48 is merged, so that I don't have to maintain two branches and push everything twice.
raylib functions often take an array and it's length as arguments. This is fine in C, because it doesn't have a concept of "fat-pointers", or "slices", but on the Zig side we try to map these array/length pairs to slices wherever possible.
This affects all of the following:
However, I would like to postpone further fixes until Zig 0.11.0 is released and #48 is merged, so that I don't have to maintain two branches and push everything twice.