Skip to content

Fixed overflowing content on 0.114 blog post #2193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cptpiepmatz merged 1 commit into from
Jul 5, 2026
Merged

Fixed overflowing content on 0.114 blog post #2193

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions blog/2026-07-04-nushell_v0_114_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -361,9 +361,6 @@ Let's see how this works with an example:

`$in` variable is now typed based on the pipeline input type of the surrounding expression.

<div style="display: grid; grid-template-columns: repeat(auto-fit, minmax(40rem, 1fr)); row-gap: 2rem; justify-items: center;">
<div>

```ansi:no-line-numbers title="Before. Error is caught at runtime."
Error: nu::shell::operator_incompatible_types

Expand All @@ -377,9 +374,6 @@ Error: nu::shell::operator_incompatible_types
╰────
```

</div>
<div>

```ansi:no-line-numbers title="After. Error is caught at parse time."
Error: nu::parser::operator_incompatible_types

Expand All @@ -393,9 +387,6 @@ Error: nu::parser::operator_incompatible_types
╰────
```

</div>
</div>

#### Better type inference of `let` bindings

`let` bindings in the middle of a pipeline, or at the end of it, are now properly typed based ont the pipeline input type.
Expand Down