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

fn cube(length, center) {
  return length
}

fn double(@x) {
  return x * 2
}
fn width() {
  return 200
}

myCube = cube(length = 200 |> double(%), center = [0, 0])
Make = and => optional in function declarations (#4577) * Make `=` and `=>` optional in function declarations And requires `:` for return types Signed-off-by: Nick Cameron <nrc@ncameron.org> * Tests Signed-off-by: Nick Cameron <nrc@ncameron.org> * Format types in function decls Signed-off-by: Nick Cameron <nrc@ncameron.org> * Require in anon function decls Signed-off-by: Nick Cameron <nrc@ncameron.org> --------- Signed-off-by: Nick Cameron <nrc@ncameron.org> 2024-11-27 15:46:58 +13:00			`fn cube(length, center) {`
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			`return length`
Move tests into simulation (#4487) Replace wasm-lib integration tests with KCL simulation tests. 2024-11-18 16:20:32 -06:00			`}`

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 double(@x) {`
Move tests into simulation (#4487) Replace wasm-lib integration tests with KCL simulation tests. 2024-11-18 16:20:32 -06:00			`return x * 2`
			`}`
Make = and => optional in function declarations (#4577) * Make `=` and `=>` optional in function declarations And requires `:` for return types Signed-off-by: Nick Cameron <nrc@ncameron.org> * Tests Signed-off-by: Nick Cameron <nrc@ncameron.org> * Format types in function decls Signed-off-by: Nick Cameron <nrc@ncameron.org> * Require in anon function decls Signed-off-by: Nick Cameron <nrc@ncameron.org> --------- Signed-off-by: Nick Cameron <nrc@ncameron.org> 2024-11-27 15:46:58 +13:00			`fn width() {`
Move tests into simulation (#4487) Replace wasm-lib integration tests with KCL simulation tests. 2024-11-18 16:20:32 -06:00			`return 200`
			`}`

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			`myCube = cube(length = 200 \|> double(%), center = [0, 0])`