Does that mean a caller doesn't need to do checks when calling vsir_block_list_add_unchecked()? :) I can certainly see the logic behind calling this _unchecked, but it seems a bit ambiguous.
Yeah, I was aware of this ambiguity. Using `_checked` would have had the same ambiguity, though: it remains unclear whether the adjective applies to the work done by the callee or to the work the caller is supposed to do.
To me the actual ambiguity resolution lies with the fact that I expect the shorter function name to be the safer one, and the name with attributes to be the one that requires more care. But I'll admit that's my own thinking.
Note that in case of e.g. d3d12_command_queue_submit_locked(), the _locked suffix means the caller locks; if we were to be consistent with that naming convention, we'd call this vsir_block_list_add_checked().
Sure, ok to go with this convention.