Bri

Just throwing stuff at the wall... ```html import {createEventDispatcher} from "svelte"; // this is wacky as all hell but kinda sorta less globals (syntax is more rigid??) type T =...

Also, wouldn't using `$$` prefixes instead of `Component` match Svelte patterns better? ```html import {createEventDispatcher} from "svelte"; type T = $$Generic; // extends boolean type X = $$Generic; // any...

A bit of syntax that Svelte sorta has already (and that isn't easily found in the documentation) is this: ```svelte ``` More to the point, I think using a comment...

> Syntax highlighters don't typically parse so the change would need to made there as well. I made the new syntax highlighter for the VSCode extension, and I will say...

My viewpoint on it goes like this: If Svelte were to deviate from HTML, what would be most intuitive? In my opinion, that's simply duplicating the comment syntax already used...

Oh also, just to throw more stuff at the wall, if Svelte adds a symbol for ignoring an attribute, I think it would make the most sense to duplicate HTML...

I'm pretty sure we're effectively in agreement, but just for the sake of discussion: > That is the only use-case though. Everything else is already covered. Personally, I am a...

I feel like rather than using typing, which wouldn't help a JS user, I think JSDoc-like comments in a `@component` doc-comment would work best. ```svelte Hello div { color: var(--color,...

> how do $$Props and $$Events currently work in JSDoc syntax? $$StyleProps could work the same way. > If there is no such support yet, you could open a new...

I really do feel like making it part of the TypeScript interfaces is... weird? Like, it makes sense for normal exported props because they are JS values and types. But...