Justifying Feature Additions to Bytecodec.

[jortsupetterson]

This thread is to evaluate whether it’s actually worth expanding bytecodec beyond its current scope.

My stance: I’d rather not add anything unless there’s a compelling reason.

Each addition introduces maintenance overhead, increases complexity, and risks diluting the goal of keeping bytecodec as a minimal, predictable set of binary helpers with strong input validation and no runtime dependencies for z-base.

If you think something truly belongs in the library, make the case:

What’s the actual use case?

Is it painful or impractical to implement outside the library?

Does it respect the current design goals?

How much does it cost us in long-term complexity/test surface?

Let’s keep the bar high. No bloat.