V4l2.Capability triggers compiler bug
Submitted by Matthew Brush
Link to original bug (#790634)
Description
The V4l2.Capability structure is missing unowned
on the reserved
field. This causes valac to generate a call to a mysterious capability_destroy
function that doesn't exist and so causes linking errors. I assume valac is meant to also generate a definition of this capability_destroy
function if it's going to call it.
Aside from the weird codegen bug it triggers in valac, just adding unowned
on the reserved
field or removing the reserved
field altogether seems to produce correct codegen.
The missing unowned
is probably also missing on all other structs with array fields (ex. SlicedVbiFormat::service_lines
[0] and SlicedVbiFormat::reserved
).
[0]: unrelated but this should also be a multi-dimensional array.