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

fn increment(@i) {
  return i + 1
}

xs = [0..2]
ys = xs
  |> map(f = increment)
  |> map(f = increment)
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 increment(@i) {`
KCL: More simulation tests (#4359) Demonstrate simulation tests where we don't care about visuals, e.g. the double-map test. The `just new-sim-test` now accepts an optional argument, `render_to_png` which can be either "true" or "false" (defaults to "true"). Tests like double_map that don't render anything can use false, rather than rendering an empty PNG with nothing in it. This means the [tests under `no_visuals/`](https://github.com/KittyCAD/modeling-app/tree/v0.26.2/src/wasm-lib/tests/executor/inputs/no_visuals) can be entirely replaced by simulation tests. This is much better! For example, I moved `double_map.kcl` from a no_visuals test to a simulation test. Here's the file: ``` fn increment = (i) => { return i + 1 } xs = [0..2] ys = xs \|> map(%, increment) \|> map(%, increment) ``` Previously the `no_visuals` test just checked that the program ran successfully without panicking. Now the simulation test lets you see the value of `xs` and `ys` and immediately see they're correct. If our map logic changes (for example, we have an off-by-one error and don't apply the `map` to the last element) it'll show up in the program memory snapshot. 2024-10-31 11:43:14 -05:00			`return i + 1`
			`}`

			`xs = [0..2]`
			`ys = xs`
Kwargs: map and reduce (#6480) Migrate array's `map`, `reduce` and `push` functions to use keyword arguments. 2025-04-25 19:09:03 -05:00			`\|> map(f = increment)`
			`\|> map(f = increment)`