TPZ5004: Wrong argument count

Compiler phase: check/runtime.

Compiler explanation: A call supplied too few, too many, or duplicate arguments for the callable shape.

Message templates. The marker ⟨value⟩ stands for text computed for the reported program.

• a protocol call ⟨value⟩.⟨value⟩(…) takes positional arguments only Source
• newtype ⟨value⟩ constructor takes 1 argument (the ⟨value⟩ to wrap), found ⟨value⟩ Source
• ⟨value⟩ takes ⟨value⟩ ⟨value⟩, found ⟨value⟩ Source
• the pipeline inserts the piped value, but this function takes no parameters Source
• this call needs ⟨value⟩⟨value⟩ ⟨value⟩, found ⟨value⟩ Source
• named arguments must follow spread arguments Source
• a spread argument cannot skip an unsatisfied fixed parameter Source
• positional arguments may not follow named arguments Source
• a protocol call ⟨value⟩(…) takes positional arguments only Source
• spread arguments require a variadic parameter Source
• this call needs ⟨value⟩ ⟨value⟩, found ⟨value⟩ Source
• the left side of >> takes exactly one argument (§11) Source
• the right side of >> takes exactly one argument (§11) Source
• a pipeline stage takes the piped value as its only argument (§11) Source
• this lambda takes ⟨value⟩ parameter(s), but a function taking ⟨value⟩ is expected Source
• record ⟨value⟩ is missing field⟨value⟩ ⟨value⟩ Source
• newtype ⟨value⟩ pattern takes 1 subpattern (the wrapped ⟨value⟩), found ⟨value⟩ Source
• enum variant ⟨value⟩.⟨value⟩ takes ⟨value⟩, found ⟨value⟩ Source

Observed for the candidate in Topaz 5.21.3. Execution

• error[TPZ5004]: this call needs 1 argument, found 0

A call must supply every required parameter. Calling a one-parameter function with no arguments is rejected with TPZ5004 at the call expression.

Compare the call with its declaration. Supply the required parameters once and use names accepted by that callable.