mirror of
https://github.com/nushell/nushell.git
synced 2024-11-22 00:13:21 +01:00
b7af715f6b
# Description Fixes: #14110 Fixes: #14087 I think it's ok to not generating instruction to `def` and `export def` call. Because they just return `PipelineData::Empty` without doing anything. If nushell generates instructions for `def` and `export def`, nushell will try to capture variables for these block. It's not the time to do this. # User-Facing Changes ``` nu -c " def bar [] { let x = 1 ($x | foo) } def foo [] { foo } " ``` Will no longer raise error. # Tests + Formatting Added 4 tests |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
This crate primarily drives the evaluation of expressions.
(Some overlap with nu-protocol)
- Provides
CallExt
Internal Nushell crate
This crate implements components of Nushell and is not designed to support plugin authors or other users directly.