31 Aug
2023
31 Aug
'23
8:26 a.m.
Mostly because it's not terribly practical to check in anything that outputs more than one or two lines. I think we should adopt the vkd3d_bytecode_buffer scheme and track the status on the vkd3d_string_buffer instead of attempting to propagate errors up from vkd3d_string_buffer_resize().
Agreed. What I don't like is that no check of allocation failure is done at all. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/310#note_43932