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
Expected behavior: b should have the same type as a, i.e. a tuple of 6 numbers Actual behavior: b has the type of a tuple of 5 numbers. Not only is this unexpected, it also doesn't match what happens at runtime where b.length == a.length as expected.
It seems to me that the problem comes from the tuple overloads of map added in #11252.
If I understand this correctly, #5453 would be needed in order to these overloads correctly for the general case.
In the meantime if there was some way of falling back to an array for map on longer tuples, that would work, e.g. adding an overload like this maybe?
Activity
Fix for #13840: Remove map tuple overloads
Array cleanup (#16223)