TC39 Delegates on 2022-05-24

01:08	<rbuckton>	yulia: I recently added additional information to the explainer for the resource management proposal based on your feedback that some additional context around how this could be integrated into DOM APIs should be included. If you have some time, could you peruse https://github.com/tc39/proposal-explicit-resource-management#relation-to-dom-apis and let me know if that was what you were looking for?
02:35	<rbuckton>	fwiw, vscode has a setting that should enable syntax highlighting: `"files.associations": { "*.emu": "html" }` I really need to dust of my ecmarkup vscode extension, I haven't had the time to work in it in a few years now
02:36	<rbuckton>	The value in a different extension is in language service functionality that could differ from regular HTML, which can't otherwise be easily distinguished from the content of the file itself.
02:37	<rbuckton>	For example, my ecmarkup extension supported go to definition and other features inside of `<emu-grammar>` tags
02:57	<snek>	ecmarkup language server when
03:11	<bakkot>	The value in a different extension is in language service functionality that could differ from regular HTML, which can't otherwise be easily distinguished from the content of the file itself. can you not tell vscode to use a particular language service, the way you can tell it to use a particular syntax?
03:49	<rbuckton>	ecmarkup language server when There is an old one I wrote several years ago, I started on a new one but have too many other commitments currently.
03:50	<rbuckton>	can you not tell vscode to use a particular language service, the way you can tell it to use a particular syntax? That's essentially one and the same, so yes. However, you probably don't want ecmarkup support enabled in every HTML file.
04:02	<bakkot>	Oh, sure, reasonable