You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The catch is that our type system doesn't yet allow us to express an arbitrary tuple where every component is Hashable. This is something we want, though, not just for Hashable but for "Printable", "Serializable" and all such protocols in the pipe, as well as the subtree notion I'm seeing around the next corner for Orchestron.
Let's call the desired feature regular tuples! My hope is that they will be as flexible as Python's common use of dict[str,object] data, while supporting static type-safety.
It feels like tuples should be hashable when when they consist of fields that are hashable individually.
I think this requires #1677
The text was updated successfully, but these errors were encountered: