Compiler improvements: labels with unused arguments

[matiwinnetou]

I found something that could be better to make our lives easier:

fn close_action_success(
  _datum: Datum,
  _validity_range: ValidityRange,
  _outputs: List<Output>,
) -> Bool {
  False
}

This code is a placeholder for now and of course this is all valid code but if I call this function using:

      close_action_success(
        datum: datum,
        validity_range: validity_range,
        outputs: outputs,
      )

obviously it will fail. I wish it worked, alternatively if I change all the arguments to _ it also doesn't work... then it fails with an error:

mati@Mateuszs-MacBook-Pro english_auction % aiken check
    Compiling aiken-lang/stdlib 43d8e740ffdf5febc59e51b7f0d5f8506115340c (/Users/mati/Devel/OpenSource/aiken/examples/english_auction/build/packages/aiken-lang-stdlib)
    Compiling aiken-lang/english_auction 0.0.0 (/Users/mati/Devel/OpenSource/aiken/examples/english_auction)
Error: aiken::parser

  × While parsing files...
  ╰─▶ I found an unexpected token '":"'.
      
     ╭─[/Users/mati/Devel/OpenSource/aiken/examples/english_auction/validators/english_auction.ak:150:1]
 150 │       close_action_success(
 151 │         _datum: datum,
     ·               ─
 152 │         _validity_range: validity_range,
     ╰────
  help: Try removing it!

of course I can always remove all arguments and it will be fine but I would have preferred to leave those arguments as a placeholder. Alternatively I can call this function with passing arguments WITHOUT using labels but simply using order of arguments (classic / typical) but this is not ideal I guess.

I would say this is post alpha and not that important now, just flagging usability / ergonomics wishes.

[rvcas]

you can accomplish that by defining your function like this:

fn close_action_success(
  datum _datum: Datum,
  validity_range _validity_range: ValidityRange,
  outputs _outputs: List<Output>,
) -> Bool {
  False
}