| 02:46 | <Domenic> | It's interesting that popular syntax highlighters have generally chosen to be kind of loose and produce nonsense output in the face of nonsense input. For some cases, like writing specs, having them be strict would be quite useful---bonus syntax checking in your build process. But for cases like writing GitHub comments, I guess you want loose. |
| 07:24 | <freddy> | thanks TabAtkins |
| 07:29 | <TabAtkins> | It's interesting that popular syntax highlighters have generally chosen to be kind of loose and produce nonsense output in the face of nonsense input. For some cases, like writing specs, having them be strict would be quite useful---bonus syntax checking in your build process. But for cases like writing GitHub comments, I guess you want loose. An issue is handling new syntaxes. Strict parsing means you'll break if there's an update to the language, or someone uses it on a proposal for something new, or someone is highlighting a fragment of syntax that you didn't expect them to start on, etc. Strict also requires a Real Parser, whereas I know the Pygments model is a pile of regexes, at least by default. That's simpler for most people to author. |
| 07:30 | <TabAtkins> | That said, the failure mode here was *weird* |
| 14:40 | <Luke Warlow (🇪🇸)> | jarhar: regarding ToggleEvent.source tests, The spec PR is merged but the tests still seem to be tentative to me, is there a PR to update them? |
| 16:06 | <jarhar> | https://chromium-review.googlesource.com/c/chromium/src/+/6621684 |