computedFn doesn't allow varying number of arguments

The computedFn function doesn't allow a varying number of arguments, between calls to the function it returns.

This is apparently already known, since the function description says:

computedFn(fn) returns a function with the very same signature. There is no limit on the amount of arguments that is accepted. However, the amount of arguments must be consistent and default arguments are not supported.

Is there a fundamental reason that you can't provide a varying number of arguments? Or has the code just not been made flexible enough yet to allow varying argument counts?

If it's the former (impossible to implement), what's the explanation for that limitation?

If it's the latter (possible to implement), then I plan to do the work of implementing it, as it's pretty important for my current use-case.

Anyway, I'm guessing it is possible, so I'm starting work on trying to implement that functionality; if it's not possible though, please let me know so I can save some time. ^_^

[potential question] Why do you need to provide a varying number of arguments?

Basically: Because that's the only way I'm able to send in an array in a way that's compatible with caching.

In more detail: I "unwrap" the array's items, and send each one in as a separate "argument" to the function. This lets the data be cached by the DeepMapEntry chain. When the function actually runs, it then reconstructs the array argument from the constituent items.

Start by locating the computedFn implementation and reading its function description to understand how argument counts are handled between calls. Done means either establishing and documenting why varying argument counts cannot work, or implementing the behavior and verifying that calls with different counts remain compatible with caching.