Grzegorz Caban a0e3ad2b70 return in reduce command closure (#7961) ... # Description Fix for #7933. I've read through code and found the obvious difference between them, where `each` command calls eval_with_early_return e89e734ca2/crates/nu-command/src/filters/each.rs (L158), while `reduce` command uses eval_block e89e734ca2/crates/nu-command/src/filters/reduce.rs (L143) That simple change seems to resolve the problem. # User-Facing Changes Allows the use of `return` in reduce closures, as per example in #7933 description. Arguably it's restoring consistency, than changing user interface. ``` [1, 2] | reduce --fold null { |it, state| ::: if $it == 1 { ::: return 10 ::: } ::: return ($it * $state) ::: } 20 ``` # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (cargo fmt --all applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.		2023-02-04 16:41:54 -06:00
..
assets	refactor html module (#5246)	2022-04-20 08:50:14 -05:00
proptest-regressions/format_conversions	add tests, deal with pipes, newlines, tabs for to nuon (#6391)	2022-09-01 14:08:19 +02:00
src	return in reduce command closure (#7961)	2023-02-04 16:41:54 -06:00
tests	Remove deprecated --numbered flag from four commands (#7777)	2023-02-02 16:59:58 -06:00
build.rs	Use variable names directly in the format strings (#7906)	2023-01-29 19:37:54 -06:00
Cargo.toml	Bump to 0.75.1 development version (#7930)	2023-01-31 23:55:29 +01:00
LICENSE	Include license text in all crates (#5094)	2022-04-08 10:47:13 +02:00