Daniel P H Fox

Actually, same issue as #664 it seems. This might be a dupe.

So I've been playing around with the bugs in this branch for a short while this evening. As best as I can tell, this branch messes up the lifetimes of...

Fixed some of the major lifetime issues - after a lot of diagnosis, it turns out the issue was that New calls were being cached, which is incorrect because scope...

 Ported the Word Game example just fine... so looks like I'll need a more complex example to figure out what's going wrong.

> if you create a tween with a repeat count of -1 then the first time its evaluated self._activeFrom is nil so it sets self._activeElapsed to self._activeDuration (which is infinity)...

Will also need to fix the infinite loop check in `change` to allow for cyclic changes if they happen through a dependency that doesn't meaningfully change (likely, this just means...

Something I realise now about the way that execution should work; the oldest graph objects should be evaluated first. Here's why; suppose that there's an Observer A which creates or...

Alright. So I've been looking into the issues that are currently blocking this, and it looks like there's a problem with re-entrant reactive updates. Specifically; if an eagerly updated object...

Creating imitations of Roblox types does feel a little bit cursed, and I'm not sure there's a strong motive to support them. I feel like the solution here isn't to...

We generally look to align with Luau, not outside libraries. As a case study of why we don't do this, we originally aligned Value's naming with React - "State" -...