Daniel P H Fox

`xpcall()` is actually pretty close to the behaviour that's wanted here. In order to catch errors, you'd need to construct children in a callback, and to be able to show...

By the way, I need opinions on what that function should actually look like / what the name of it should be / what the names of the callbacks should...

An alternate, more component-centric design using currying: ```Lua local function Safe( scope: Scope, component: (Scope, Props) -> Success ) return function( props: Props & { OnError: (err: unknown) -> Fail...

I think it'll be best to implement this as: ```Lua Safe { try = function() ... end, fallback = function(err) ... end } ```

In combination with #300, this also means that observers of constant values would be reduced to a table of either no-ops or functions that execute whatever callback is given to...

There's a really clever way to do this under both eager and lazy execution (#144) - at the very start of the `Computed` constructor, run the processor function in a...

It's probably important to clarify that this optimisation only applies to state objects that don't specify any additional methods. For example, while `Tween` could be dissolved away, `Spring` could not,...

I'm probably going to mark this issue as blocked again for the time being. Considerations around nested state objects nullify a bit of the benefit of a change like this,...

This idea extends to `Tween` and `Spring` objects, too. Updating post to match.

This seems mostly fine, but it'd be nice if it were more general and didn't implicitly make assumptions about what classes batch together. Ideally it'd either be a general rule...