fish-shell/tests/checks/return.fish

#RUN: %fish -C 'set -l fish %fish' %s | %filter-ctrlseqs
# Some tests of the "return" builtin.

$fish -c 'return 5'
echo $status
# CHECK: 5

$fish -c 'exit 5'
echo $status
# CHECK: 5

$fish -c 'echo foo; return 2; echo bar'
# CHECK: foo
# but not bar
echo $status
# CHECK: 2

$fish -ic 'echo interactive-foo; return 69; echo interactive-bar'
# CHECK: interactive-foo
# but not bar
echo $status
# CHECK: 69

# Verify negative return values don't cause UB and never map to 0
function empty_return
    return $argv[1]
end

for i in (seq -- -550 -1)
    empty_return $i
    if test $status -eq 0
        echo returning $i from a fish script maps to a $status of 0!
    end
end
# CHECK:
Extended & human-friendly keys See the changelog additions for user-visible changes. Since we enable/disable terminal protocols whenever we pass terminal ownership, tests can no longer run in parallel on the same terminal. For the same reason, readline shortcuts in the gdb REPL will not work anymore. As a remedy, use gdbserver, or lobby for CSI u support in libreadline. Add sleep to some tests, otherwise they fall (both in CI and locally). There are two weird failures on FreeBSD remaining, disable them for now https://github.com/fish-shell/fish-shell/pull/10359/checks?check_run_id=23330096362 Design and implementation borrows heavily from Kakoune. In future, we should try to implement more of the kitty progressive enhancements. Closes #10359 2024-03-30 23:10:12 +08:00			`#RUN: %fish -C 'set -l fish %fish' %s \| %filter-ctrlseqs`
Let "return" exit a script (#8148) Currently, if a "return" is given outside of a function, we'd just throw an error. That always struck me as a bit weird, given that scripts can also return a value. So simply let "return" outside also exit the script, kinda like "exit" does. However, unlike "exit" it doesn't quit an interactive shell - it seems weird to have "return" do that as well. It sets $status, so it can be used to quickly set that, in case you want to test something. 2021-07-22 04:33:39 +08:00			`# Some tests of the "return" builtin.`

			`$fish -c 'return 5'`
			`echo $status`
			`# CHECK: 5`

			`$fish -c 'exit 5'`
			`echo $status`
			`# CHECK: 5`

			`$fish -c 'echo foo; return 2; echo bar'`
			`# CHECK: foo`
			`# but not bar`
			`echo $status`
			`# CHECK: 2`

			`$fish -ic 'echo interactive-foo; return 69; echo interactive-bar'`
			`# CHECK: interactive-foo`
			`# but not bar`
			`echo $status`
			`# CHECK: 69`
Test return builtin doesn't map negative numbers to zero Prior to 1811a2d, the return value for negative return codes was UB and I'd witnessed both expected cases like -256 mapping to a $status of 0 and unexpected cases like a return value of -1 mapping to a $status of 0. As such, this doesn't test just one fixed return value but the entire range from negative multiples of 256 all the way down (rather, up!) to -1. 2022-09-26 01:37:10 +08:00
			`# Verify negative return values don't cause UB and never map to 0`
			`function empty_return`
			`return $argv[1]`
			`end`

Use -- before seq for negative numbers busybox seq was complaining about the command: seq -550 -1 because it was trying to interpret -550 as a flag. Use -- to prevent this. 2022-10-24 04:42:53 +08:00			`for i in (seq -- -550 -1)`
Test return builtin doesn't map negative numbers to zero Prior to 1811a2d, the return value for negative return codes was UB and I'd witnessed both expected cases like -256 mapping to a $status of 0 and unexpected cases like a return value of -1 mapping to a $status of 0. As such, this doesn't test just one fixed return value but the entire range from negative multiples of 256 all the way down (rather, up!) to -1. 2022-09-26 01:37:10 +08:00			`empty_return $i`
			`if test $status -eq 0`
			`echo returning $i from a fish script maps to a $status of 0!`
			`end`
			`end`
			`# CHECK:`