add tuple map class

[bmschmidt]

We often have to use a tuple of things as indexes in deepscatter. This creates a class that allows accessing things by string (or object) indexes so that you can do things like:

const a = new TupleMap();
a.set(["foo", "bar"], 2)
a.get(["foo", "bar"])
// == 3

Even though the objects don't match.

---

🚀	This description was created by 48c5da6

feat: add TupleMap class for tuple-based indexing

Summary:

Introduces TupleMap class for efficient tuple-based indexing with string or object keys, supporting various methods and cleaning up empty maps.

Key points:

• Introduces TupleMap class in src/utilityFunctions.ts for tuple-based indexing.
• Supports set, get, has, and delete methods.
• Allows string or object keys in tuples.
• Handles non-matching object keys gracefully.
• Cleans up empty nested maps after deletion.
• Example usage: a.set(["foo", "bar"], 2); a.get(["foo", "bar"]).

---

Generated with ❤️ by ellipsis.dev

[bmschmidt]

• add tuple map class #139 : 2 dependent PRs (#140 , #142 ) 👈
• Remove the deferred functions queue #138
• longer .gitignore #137
• 09 04 add ellipsis code review instructions #136
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bmschmidt and the rest of your teammates on Graphite

[bmschmidt]

Merge activity

• Sep 19, 3:05 PM EDT: @bmschmidt started a stack merge that includes this pull request via Graphite.
• Sep 19, 3:06 PM EDT: Graphite couldn't merge this pull request because a downstack PR 09 04 add ellipsis code review instructions #136 failed to merge.
• Sep 19, 10:58 PM EDT: @bmschmidt started a stack merge that includes this pull request via Graphite.
• Sep 19, 11:09 PM EDT: Graphite rebased this pull request as part of a merge.
• Sep 19, 11:10 PM EDT: @bmschmidt merged this pull request with Graphite.

[ellipsis-dev]

Using objects as keys in TupleMap can lead to unexpected behavior because object references are compared, not their content. Consider using a serialization method for object keys to ensure consistent behavior.

[ellipsis-dev]

The logic to traverse the map is repeated in set, get, has, and delete methods. Consider refactoring this into a separate method to adhere to the DRY principle.