The above works great. However, the problem comes when I want to use literal types for my legal values. In my code, I want to do that so I can make sure I define a "handler" for every legal value: const legalValues = <const>["a", "b", "c"]; // later on... // Because legalValues entries are literal types, // I get a compiler error if I forget to define any behaviors const behaviors: { [K in typeof legalValues[number]]: any } = { a: something, b: somethingElse, c: anotherThing };

We also get a hook to alter commit messages so that they include a common suffix. We can then use this to set up a server-side hook that refuses changes that don’t have this in their messages.

Mutually exclusive categories can be beneficial. If categories appear several places, it's called cross-listing or polyhierarchical. The hierarchy will lose its value if cross-listing appears too often. Cross-listing often appears when working with ambiguous categories that fits more than one place.

RPython puts some constraints on the Python language such that a variable's type can be inferred at compile time.

Instead of one big code pile, activities will gently enforce a clean, standardized way for organizing code.

They are an abstraction that will save code and bugs, and introduce strong conventions.

The office door is locked at 5pm. We work hard, but at 5 it's time to go home!

On the other hand, we could impose restrictions to the feature in order to avoid these hard paths.

Instead, my purpose is to illustrate why an alternative approach — based on Single File Components with real CSS — is so damn delightful.

By enforcing this practice, Svelte can make some assumptions that simplify your code.