1.3.0

[yannham]

Version 1.3

Version 1.3 includes several new optimizations following reports of long evaluation time for medium-sized codebase. The command-line interface (CLI) has been reworked to be more user-friendly, at the cost of breaking changes: see below. Finally, the LSP has seen continuous improvement as well.

Breaking changes

• @vkleen improved the CLI UX in numerous ways in Make eval an explicit subcommand and restructure the CLI somewhat #1632

  • The file argument is now argument positional. That is, instead of running nickel export -f config.ncl, now use nickel export config.ncl instead.
  • Every command which can take a file argument can now take several of them. The program parsed from the files are then merged before applying the action. For example, the new nickel export config1.ncl config2.ncl config3.ncl is the equivalent of the previous nickel export <<< '(import "config1.ncl") & (import "config2.ncl") & (import "config3.ncl")'
  • Evaluation is now an explicit subcommand, instead of being the default action. Instead of running nickel -f config.ncl to evaluate a file, use nickel eval config.ncl instead.

• Not a breaking change per se, because the customize mode is experimental, but @yannham introduced a new syntax for customize mode in New syntax for customize mode #1709. Instead of dynamically generating a CLI where arguments are field paths, the new customize mode CLI directly take assignments written in a Nickel-like syntax as positional arguments. For example, in 1.2, the command:

  $ nickel eval -f confing.ncl -- \
    --input.field1 '"Value"' --input.flag false \
    --override output.bar 0`

  now becomes

  $ nickel eval config.ncl -- \
    'input.field1="Value"' input.flag=false \
    --override output.bar=0`

Fixes

• Fix record.update by making record.insert act consistently by @yannham in Fix record.update by making record.insert act consistently #1669

Tooling

• LSP:
  • implement type-based completion in the new completer by @jneem in Type-based completion in the new completer #1577
  • Improve context completion by @jneem in Context completion #1584
  • Take the ancestor path into account when env-completing from uncles. by @jneem in Take the ancestor path into account when env-completing from uncles. #1661
  • Add goto support for pattern bindings by @jneem in Add goto support for pattern bindings #1665
  • Add cousin search to goto and hover by @jneem in Add cousin search to goto and hover #1670
  • Improve hover output for let patterns by @jneem in Improve hover output for let patterns #1696
  • First prototype of contract evaluation by @jneem in First prototype of evaluation #1672
• LSP: a large refactoring work by @jneem to get rid of the old and
  hard-to-maintain code analysis implementation
  (Convert symbols request away from the linearizer #1623,
  Hover support without the linearizer #1629,
  Nuke the linearizer #1658,
  Remove/rename the Linearizer trait #1663)
• Honor nostdlib in customize mode as well by @vkleen in Honor nostdlib in customize mode as well #1634
• Add the list subcommand to the customize mode by @yannham in New syntax for customize mode #1709
• add %eval_nix% primop for Nix interop by @Radvendii in
  add %eval_nix% primop #1465 (requires to build with the
  corresponding experimental feature enabled)
• Get rid of shallow_repr and print full terms in error messages by @yannham in
  Get rid of shallow_repr and print full terms #1676
• Add suggestions to the error message when misspelling a record field by @yannham in Add suggestions when misspelling a record field #1710
• Add a --field argument to subcommands to target a specific field whenever it makes sense by @yannham in Add a --field argument to subcommands whenever it makes sense #1712

Optimizations

• Contract elision for static types by @yannham in Contract elision for static types #1671
• Implement contract deduplication optimization by @yannham in Implement contract deduplication optimization #1631
• Array contract deduplication by @yannham in Array contract deduplication #1674
• Get rid of most generated variables by @yannham in Get rid of most generated variables #1679

Documentation

• Fix invalid example code in doc of blame_with_message by @bgni in Fix invalid example code in doc of blame_with_message #1689
• Fix doc, example code for pipe lacks prefix by @bgni in Fix doc, example code for pipe lacks prefix #1692
• change nickel-nix to organist by @Radvendii in change nickel-nix to organist #1691

New Contributors

• @bgni made their first contribution in Fix invalid example code in doc of blame_with_message #1689
• @giorgiga made their first contribution in Reword impl of partial_cmp for Ident, LocIdent #1697

Full Changelog: 1.2.2...1.3.0

---

This discussion was created from the release 1.3.0.

[9128305]

Hi, why does the latest release not contain binaries?

[vkleen]

It looks like our artifact building workflow has broken without anyone noticing. Thanks a lot for bringing this to our attention! I'll see if I can figure out why.

[yannham]

Hello @9128305, an access token has expired. I have started the workflow again, if everything goes right, the binaries should be automatically updated in the next hour or so.

[9128305]

@yannham Thanks, but I still don't see binaries in the 1.3.0 release.
upd: it's still running https://github.com/tweag/nickel/actions/runs/6894002012/job/19090189477

[vkleen]

Something's still broken with the AWS setup. I'm looking into it :)

[vkleen]

I got it worked out and we have binaries in the release now 🎉