The CALL byte code currently imposes limits of 255 named and 255 positional arguments to a call. This limit was today exceeded by a call in Google's build system. The task of this issue is to decide whether to raise the limit, and if so to what value, and implement the change; or to document the restriction. Perhaps there is a case for imposing a limit--the same one--on all implementations, through a spec change.
I have yet to hear why replacing the sequence of call arguments with a list is not a viable workaround.
Google internal issue b/399521968.
The CALL byte code currently imposes limits of 255 named and 255 positional arguments to a call. This limit was today exceeded by a call in Google's build system. The task of this issue is to decide whether to raise the limit, and if so to what value, and implement the change; or to document the restriction. Perhaps there is a case for imposing a limit--the same one--on all implementations, through a spec change.
I have yet to hear why replacing the sequence of call arguments with a list is not a viable workaround.
Google internal issue b/399521968.