modeling-app/rust/kcl-lib/tests/argument_error/input.kcl

fn f(@i) {
  return 5
}

map(f, f = [0, 1])
KCL: User-defined KCL functions in examples etc now use keywords (#6603) Preparing for the removal of positional functions from the language. The first big step is to change all our KCL code examples, test code, public samples etc to all use keyword functions. Apologies for how large this PR is. Most of it is: - Changing example KCL that defined its own functions, so the functions now use keyword arguments rather than positional arguments. E.g. change `cube([20, 20])` to be `cube(center = [20, 20])`. - Some parts of the code assumed positional code and didn't handle keyword calls, e.g. the linter would only check for positional calls to startSketchOn. Now they should work with either positional or keyword. - Update all the artifacts This does _not_ remove support for positional calls. That will be in a follow-up PR. 2025-05-01 11:36:51 -05:00			`fn f(@i) {`
Fix argument error to point to the arg at the call site (#4533) * Fix argument error to point to the arg at the call site * Change MemoryFunction to accept Vec<Arg> instead of Vec<KclValue> * Rename variable to be clearer * Fix one more argument error message * Clean up from PR feedback 2024-11-21 13:10:03 -05:00			`return 5`
			`}`

KCL: User-defined KCL functions in examples etc now use keywords (#6603) Preparing for the removal of positional functions from the language. The first big step is to change all our KCL code examples, test code, public samples etc to all use keyword functions. Apologies for how large this PR is. Most of it is: - Changing example KCL that defined its own functions, so the functions now use keyword arguments rather than positional arguments. E.g. change `cube([20, 20])` to be `cube(center = [20, 20])`. - Some parts of the code assumed positional code and didn't handle keyword calls, e.g. the linter would only check for positional calls to startSketchOn. Now they should work with either positional or keyword. - Update all the artifacts This does _not_ remove support for positional calls. That will be in a follow-up PR. 2025-05-01 11:36:51 -05:00			`map(f, f = [0, 1])`