type.argument_count

A call passes more or fewer values than the function or action it calls has parameters.

Area 3, Logic; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

Your own functions and actions take their values in order, one for each parameter, and no parameter has a default. A call that passes too few leaves a parameter with no value, and one that passes too many has a value with nowhere to go. Jadpo won't fill in a missing value or drop an extra one, because either would run the call on values you didn't write.

What it looks like

main.jadpo:

type Name = Text {}function choose(first: Name, second: Name) -> Name {    return first}function incomplete(name: Name) -> Name {    return choose(name)}

  |8 |     return choose(name)  |                  ^^^^^^ 1 given

(agent) at the end of the next: line means your coding agent can make the fix itself.

Passing too many values is the same error, and its next: line says to remove the extra one:

main.jadpo:

type Name = Text {}function shout(name: Name) -> Name {    return name}function twice(name: Name, other: Name) -> Name {    return shout(name, other)}

  |8 |     return shout(name, other)  |                 ^^^^^^^^^^^^^ 2 given

How to fix it

If a value is missing, pass one for every parameter, in the order the signature lists them:

function incomplete(name: Name, fallback: Name) -> Name {    return choose(name, fallback)}

choose gets name as first and fallback as second.

If a value is extra, remove it:

    return shout(name)

shout gets the one value it takes. If the call needs the extra value, the function needs a parameter for it: add one to its signature, and pass it at every call.

Related

• Signatures and settings
• Calling