You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature comes from something that was previously possible using the raylib bindings.
Until around dev-2023-11, the Color type from raylib was defined as a struct so we could write code like this and it was pretty obvious what it would do:
x: raylib.Color = { r = 127, g = 0, b = 127, a = 255 }
But since then (after this more precisely) this type is defined as a fixed array, which allows for more flexibility but also means that the previous code no longer compiles since those fields don't actually exist in an array.
My request is to allow for this kind of syntax for initializing arrays, making the language more consistent.
The text was updated successfully, but these errors were encountered:
This feature comes from something that was previously possible using the raylib bindings.
Until around dev-2023-11, the Color type from raylib was defined as a struct so we could write code like this and it was pretty obvious what it would do:
But since then (after this more precisely) this type is defined as a fixed array, which allows for more flexibility but also means that the previous code no longer compiles since those fields don't actually exist in an array.
My request is to allow for this kind of syntax for initializing arrays, making the language more consistent.
The text was updated successfully, but these errors were encountered: