eval scope

Is the following a bug or a feature?

eval set -l foo bar
if not echo "bar" | string match -q $foo
    echo Assertion failed!
end

eval isn't explicitly documented as creating a scope.

(note that this "feature" caused some consternation in the implementing of #4442)

Provide feedback