Daniel P H Fox

`Usable` could be a good proposal, too.

> Verbose isnt always bad thing. > In this case its clear as day what CanBeState means, while something like Dynamic doesn't get across immediately > CanBeState isnt even that...

Perhaps a name like `MayChange` helps retain some of the original clarity while still moving away from assuming knowledge of state objects.

After some further discussion in the community Discord channel, we considered a few more names: - `Describes` - `Contains` - `Becomes` - `Into` - `UsedAs` - `As` - `StateOf` -...

The symmetry of `type Use = (UsedAs) -> T` is quite nice.

After talking with some more groups, common opinion seems to be that the clarity of `UsedAs` outweighs the conciseness of `As`, so (at least for the time being) I think...

For what it's worth, I'm now looking to implement much of this on the backend as part of #273. I don't plan to expose it as a usable API in...

Since the backend for this is now merged, I'm going to close this PR. To implement this, all that's needed now is the front end, which renders most of this...

New syntax for colour manipulation is outside the scope of the linked issue and should really be discussed elsewhere, please stick to the existing API surface for now. This is...

I think it'd be useful to pull in concepts from #220 for the backend implementation of the `For` objects. This won't be exposed to users yet - and it probably...