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
We need a t.readonlyTuple, which is an abstraction to flow(t.tuple, t.readonly). We can't really use this flow solution because t.tuple has overloads and flow takes only the first one (which is an unary tuple), but t.readonlyTuple should support all available overloads (up to penta-tuple).
We already have t.readonlyArray, so it makes sense to have the same abstraction also for t.tuple.
The text was updated successfully, but these errors were encountered:
I found many use cases in my firm to use t.readonlyTuple , it will be much helpful for us
it make sense to have readonlyTuple sense we have readonlyArray.
🚀 Feature request
Current Behavior
Currently we have
t.tuple
andt.readonly
.Desired Behavior
We need a
t.readonlyTuple
, which is an abstraction toflow(t.tuple, t.readonly)
. We can't really use thisflow
solution becauset.tuple
has overloads andflow
takes only the first one (which is an unarytuple
), butt.readonlyTuple
should support all available overloads (up to penta-tuple).We already have
t.readonlyArray
, so it makes sense to have the same abstraction also fort.tuple
.The text was updated successfully, but these errors were encountered: