string ones are those most of the Rubyists remember.

Generate type with the index signature: interface RandomMappingWithIndexSignature { stringProp: string; numberProp: number; [propName: string]: string | number | undefined; }

Introduce behaviour that is likely to surprise users. Instead have due consideration for patterns adopted by other commonly-used languages.

In my opinion, this single-tab Refresh behavior strongly violates the principle of least surprise, and it doesn’t help us to maintain code consistency or data consistency.

What I believe should happen is the Svelte compiler should, when a promise is passed to onMount, realise that a promise has been passed, and await the result of the function to be used as the onDestroy function. i.e, it should behave the exact same way for an async function as it does for a non-async function (if this is possible)

The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.

It’s even worse that there’s no alternative method that does the unsurprising thing IMO.

The "unsurprising" thing here would generally be to maintain the order, for instance, and subtract the first or last instance...

Code doing surprising and slightly nonsensical things... I'm weary now. And that's with ruby being more consistent than most!

In interface design, always do the least surprising thing