Daniel P H Fox

I've been working on more deep code bases that move heavily away from instances as a way of defining hierarchy, and I realise that instance based context does not solve...

Actually, if we force users to sample the context at a conventional point rather than allowing free form usage, we could use the same system as the automatic dependency manager;...

I think we can move forward with this most recent idea. We just need to be careful about how exactly we present the API surface.

Here's my idea for how things should be presented: I propose calling them `Contextual` - this lines up with common naming for this sort of feature. I did consider `Context`...

An interesting point to consider; should `Contextual` hold one value per coroutine, or one value globally? Per-coroutine would allow some level of yielding support, and would probably be more efficient...

Another point to consider; what is the value of a `Contextual` whose value has not been set? My suggestion would be to match whatever behaviour we implement for `Eventual` -...

Here's a somewhat realistic example of how this API might be used to implement a dynamic theme system. ```Lua local themeColours = { buttonBG = {dark = Color3.new(0.5, 0.75, 1),...

>* Tweens should support things like rotation, or finite number fields (e.g. with rotations, 0-360, and 270 can be considered to be 90 degrees distance to 0 degrees because 0...

Here's the list of inbuilt displacement curves I'm thinking of supporting (relatively final): - analytical spring - cubic bezier - standard tween curves (not just Roblox's) - exponential decay -...

Wrote about this on Technical Fluff: https://fluff.blog/2024/04/14/evolving-fusions-execution-model.html I plan to get started on this imminently. I have things blocked on this right now, so I'll offer to take over from...