Closed haochenuw closed 4 weeks ago
Relevant PR: https://github.com/bincode-org/bincode/pull/625 The entire array implementation was not compatible with bincode 1, so we ripped it out and fixed that issue.
That PR ends with:
They may be re-added in the future.
So I think this option is still open
One question I have is why you would want to care if bincode writes array lengths or not. What is your use case?
I am not a direct user so cannot comment on that. If the user shouldn't care, why was this struct exposed to the public?
On Thu, Oct 3, 2024 at 9:40 PM Trangar @.***> wrote:
One question I have is why you would want to care if bincode writes array lengths or not. What is your use case?
— Reply to this email directly, view it on GitHub https://github.com/bincode-org/bincode/issues/724#issuecomment-2392808746, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7YZSCVFCAQM3E6FHVXMUDZZYL4XAVCNFSM6AAAAABPKD6Q3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSHAYDQNZUGY . You are receiving this because you authored the thread.Message ID: @.***>
If the user shouldn't care, why was this struct exposed to the public?
That's why we removed it 😄
Backwards compatibility is not something we guarantee before the final stable release of 2.0. If absolute stability is necessary the 1.0 branch should be used instead.
It seems between these releases the following
was removed. This is a breaking change since clients could be using the struct in their code. Could this be fixed?