Re: [quicwg/base-drafts] don't allow 0 as a packet number (#832)

[MikkelFJ <[e-mail]>]

I see the argument of avoiding sentinels, but at least in the C programming language, there is a massive amount of boilerplate code to initialize various structs that could just have been zeroed. There there are numerous additional checks to see if a value is uninitialized instead of just comparing with the previously received value. A much simpler check is to ensure that whatever you receive is larget than what you have: it then becomes illegal to send zero. But it is also illegal to send something smaller in many cases, for example data limits. In this context treating 0 as special makes a lot sense. From an algebraic point of view, 0 also has special signficance amongst the countable objects.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/832#issuecomment-336472424