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
When we have list of a single type (string, integer, etc), we are setting the array as signature. It implies that the function argument needs an array initialisation to make it works, when we could simplify the API changing it for variadic arguments.
Should this be gated by a veneer or should we change every array that is the last argument?
What's the expectation of retrocompatibility? If this change is made, places where builder functions are called with arrays will not work on the functions that take in variadic arguments
When we have list of a single type (string, integer, etc), we are setting the array as signature. It implies that the function argument needs an array initialisation to make it works, when we could simplify the API changing it for variadic arguments.
Go:
TS:
The text was updated successfully, but these errors were encountered: