After PR #80, RawObject::raw is mc_width + size_bytes long while size_bytes still reports the MS verbatim — so raw.len() != size_bytes on R2010+. That is correct (the MS excludes the record's own MC) but is a latent trap for API consumers who assume the two agree. Before the API stabilises for 0.2.0, either rename size_bytes to declared_size_bytes or add an explicit RawObject::len()/byte_len() and document the framing (MS field | MC field | MS bytes | CRC) on the type.
Follow-up from PR #80.
After PR #80, RawObject::raw is mc_width + size_bytes long while size_bytes still reports the MS verbatim — so raw.len() != size_bytes on R2010+. That is correct (the MS excludes the record's own MC) but is a latent trap for API consumers who assume the two agree. Before the API stabilises for 0.2.0, either rename size_bytes to declared_size_bytes or add an explicit RawObject::len()/byte_len() and document the framing (MS field | MC field | MS bytes | CRC) on the type.
Follow-up from PR #80.