Daniel P H Fox

We use `table.pack` because it gives us a `n` field, which can later be used with `table.unpack` to ensure we don't miss out values returned after nils.

Thanks for bringing this up! This has been something on our radar for a while, so I think this is definitely something we should expose in some form. An interesting...

The main problem here is that ColorSequence does not meet the criteria for animatability: > If a data type can reasonably be represented as a fixed-length array of numbers, then...

> However, I don't think that is grounds to eliminate entire datatypes. There are cases that don't work, but that doesn't mean there aren't case that do. I don't intend...

So I've been ruminating on this ever since I kicked this particular can down the v0.3 road. I think the right move is probably to keep it simple. Instead of...

I'll take the opportunity to update the style guide too, since it's been decaying for years. Here's a draft of what I'm working on: [Fusion Style Guide.md](https://github.com/dphfox/Fusion/files/12458963/Fusion.Style.Guide.md) Hopefully it's more...

I veto any metatables, ever™. (only half joking there. stick to simple primitives! metatables confuse junior devs)

By the way, I agree with this premise. Feel free to bikeshed names here. I only named it this way because I cared more about having the thing implemented rather...

> Call it `doCleanup`. I like that idea. It matches the `doNothing` name and also concisely indicates it's an action. > I would prefer that `Cleanup` gets renamed to `OnDestroy`....

We'll rename it to `doCleanup` in v0.3. Thanks for the feedback everyone.