What is the role of malsplitbinary_cursor_get_bitfield_length?

[gbonnefille]

The function malsplitbinary_cursor_get_bitfield_length gives a result really different from the bitfield_length attribute member of malsplitbinary_cursor_t. And the result seems incorrect when used for a cursor created by a decoder (cf. malsplitbinary_decoder_cursor_init).

Should we remove this function?
Should we initialise the most_significant attribute member in the decode context?
Should we rename this function?

Nevertheless, the bitfield_length attribute member contains the length (in bit) of the effective bitfield, while the malsplitbinary_cursor_get_bitfield_length returns the length (in byte) of the bitfield plus its encoded length.