Darien Maillet Valentine

Sounds great to me. A lot of the notes from early on are likely either outdated or not especially important, so don’t feel obligated to retain stuff that you don’t...

This is an example of a more general thing which we currently allow in nearly all cases without attempting to mark invalidity: one assignment expression following another without a semicolon...

(tagging both 'bug' and 'enhancement' wouldn’t quite capture the nature of this issue like _bughancement_ does)

Just an update: I dug into the ASI question more today. The logic can be generalized to address the whole category in theory, but it still fails under most common...

I’ll have access to a *nix machine again shortly, btw — so if this is a chore and your motivation for addressing it is only that I ran into it...

Sounds good. I would guess this can be added following the pattern @blake-regalia has established for other tagged template cases if a sublime syntax def for pug already exists. Otherwise...

Nice. I wonder if we should allow just recognizing certain “well-known” tags like “pug” without the hint comment? It seems sufficiently unlikely to me that the name “pug” would appear...

I seem to run into a bug with the pattern `document.body.innerHTML=flags//whoops` ;)

The behavior described here appears consistent with [UTS #46](https://www.unicode.org/reports/tr46)’s `ToASCII` with `UseStd3ASCIIRules` set to `true`. It is “strongly recommended” to do so there, but the reason the parameter can be...

This threw me off too. I was expecting `createElement(Fragment, {}, ...nodes)` treatment for cases like this given the positions will be static and keying is known to be unnecessary up-front....