sokol API changes #23082
-
I have code that worked with sokol_gp but last commits was updated with the latest sokol. The API has changed, for instance the file's typedef struct sg_shader_desc {
uint32_t _start_canary;
sg_shader_function vertex_func;
sg_shader_function fragment_func;
sg_shader_vertex_attr attrs[SG_MAX_VERTEX_ATTRIBUTES];
sg_shader_uniform_block uniform_blocks[SG_MAX_UNIFORMBLOCK_BINDSLOTS];
sg_shader_storage_buffer storage_buffers[SG_MAX_STORAGEBUFFER_BINDSLOTS];
sg_shader_image images[SG_MAX_IMAGE_BINDSLOTS];
sg_shader_sampler samplers[SG_MAX_SAMPLER_BINDSLOTS];
sg_shader_image_sampler_pair image_sampler_pairs[SG_MAX_IMAGE_SAMPLER_PAIRS];
const char* label;
uint32_t _end_canary;
} sg_shader_desc; while the current V's is typedef struct sg_shader_desc {
uint32_t _start_canary;
sg_shader_attr_desc attrs[SG_MAX_VERTEX_ATTRIBUTES];
sg_shader_stage_desc vs;
sg_shader_stage_desc fs;
const char* label;
uint32_t _end_canary;
} sg_shader_desc; How often V language is expected to keep the pace with sokol updates? I was using |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There is no expectation of V keeping pace with sokol updates. They happen when someone interested enough in doing so submits a PR. |
Beta Was this translation helpful? Give feedback.
There is no expectation of V keeping pace with sokol updates. They happen when someone interested enough in doing so submits a PR.