Ensure memory usage doesn't pass a certain threshold under average conditions

[Ratstail91]

Toy_Bucket has the capacity to expand indefinitely, which is bad in practice.

I need to add a test that specifically checks the total memory usage remains below a specific threshold (or series of thresholds) under certain conditions.

Related to commit d3b59eb

[Ratstail91]

I think... putting the buckets into the scopes might work (function scopes that are no longer needed can be released), but there's an additional issue of strings that get copied refcounted around needing the original memory intact. Would strings need to reference their scope of origin?

...or should the buckets have been refcounted from the beginning?

Things stored in buckets:

• ASTs
• scopes
• strings
• functions

Things stored in malloc/realloc:

• buckets
• arrays
• tables
• stacks
• compiler escape arrays (minor detail)
• module bundles (not relevant for now)

If string & scope pointed to their Toy_Bucket of origin, instead of tracking their own refs, buckets that aren't needed anymore could be freed? Definitely worth a try.

[Ratstail91]

I just realized neither string nor scope are actually freed until the bucket itself is freed... oops.

[Ratstail91]

I know what I wrote is literally "I wonder if garbage collection is a good idea", but it took a while to reach that point.

I'm not gonna worry about the path I took, only where I'm going from here. To wit:

• Rename buckets to "arenas", this will codify the different approach in my mental framework
• Add reference counting to arenas
• Adjust the dependent structures and routines to use the arena's reference counting
• Implement explicit garbage collection