Date: Sun, 06 Jan 2019 08:25:47 -0800
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab4086e0228cbdeae6cdc1f670f1afef09e15ab0d192cf000000011849ee0b92a169ce179e43e2@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2299/451754606@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2299@github.com>
References: <quicwg/base-drafts/issues/2299@github.com>
Subject: Re: [quicwg/base-drafts] consider making the varint encoding unique
 (#2299)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c322c0b94c3e_61373fa85a4d45bc9410cc";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HcHuvfGzNa0JNEY2tdFuwFaivds>


----==_mimepart_5c322c0b94c3e_61373fa85a4d45bc9410cc
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

> Losing the flexibility afforded by allowing fixed-size varints is one way to fix the clumsy language. The other way is to fix the clumsy language.

It's not only the language that's clumsy. The fact that we have to make this distinction at all is clumsy.
I see little value in having flexibility where it's not needed, especially if it adds weird corner cases elsewhere. I'm aware that reserving a longer value and filling it in later is a lazy way to implement the varint encoding, but I didn't find it particularly hard to write my code in a way that allows me to always use the optimal encoding.

-- 
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/2299#issuecomment-451754606
----==_mimepart_5c322c0b94c3e_61373fa85a4d45bc9410cc
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<blockquote>
<p>Losing the flexibility afforded by allowing fixed-size varints is one =
way to fix the clumsy language. The other way is to fix the clumsy langua=
ge.</p>
</blockquote>
<p>It's not only the language that's clumsy. The fact that we have to mak=
e this distinction at all is clumsy.<br>
I see little value in having flexibility where it's not needed, especiall=
y if it adds weird corner cases elsewhere. I'm aware that reserving a lon=
ger value and filling it in later is a lazy way to implement the varint e=
ncoding, but I didn't find it particularly hard to write my code in a way=
 that allows me to always use the optimal encoding.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2299#issuecomment-451754606">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqySP=
ikYCw_NI4EiuLAfAs1mCYIoBks5vAiOLgaJpZM4ZyX3n">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq3u0PMXUXvtyOTdYfnQWYwwF=
xAWXks5vAiOLgaJpZM4ZyX3n.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
marten-seemann in #2299: \u003e Losing the flexibility afforded by allowi=
ng fixed-size varints is one way to fix the clumsy language. The other wa=
y is to fix the clumsy language.\r\n\r\nIt's not only the language that's=
 clumsy. The fact that we have to make this distinction at all is clumsy.=
\r\nI see little value in having flexibility where it's not needed, espec=
ially if it adds weird corner cases elsewhere. I'm aware that reserving a=
 longer value and filling it in later is a lazy way to implement the vari=
nt encoding, but I didn't find it particularly hard to write my code in a=
 way that allows me to always use the optimal encoding."}],"action":{"nam=
e":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2299#=
issuecomment-451754606"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2299#issuecomment=
-451754606",
"url": "https://github.com/quicwg/base-drafts/issues/2299#issuecomment-45=
1754606",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c322c0b94c3e_61373fa85a4d45bc9410cc--