* Make `eval` CLI explicit and remove `-f`
* Implement multiple file inputs as merging
* Use `add_string` instead of `add_term`
* `format` cannot create files anymore
* Update snapshot tests
* Separate customize mode from the `export` subcommand
* Decouple customize mode from export and make it available for every evaluation
* Disable an `unused_mut` warning
* Apply suggestions from code review
Co-authored-by: jneem <joeneeman@gmail.com>
* Add a short option for `export --format`
* Update cli/src/eval.rs
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
---------
Co-authored-by: jneem <joeneeman@gmail.com>
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
Because of #1228 we syntactically forbid contracts from containing free
type variables. This was implemented in #1271 and #1272. As a result,
the double contract application in #1194 became dead code. This PR
removes the `%dualize%` primop, the `dualize` field in `Label` and the
double application logic when constructing recursive environments for
records.
* Run a REPL session when checking `nickel #repl` snippets
* Adjust examples in the manual for new checks
* Fix some leftover error messages
* Address code review
* Assume -> ApplyContract
At the very beginning of Nickel, the duality between a type annotation and
contract annotation was reflected in their original naming, the assume
construct (contract annotation) and the promise construct (a type
annotation).
This terminology isn't used anymore, and isn't very telling for new
contributors. This PR get rid of old references to `Assume` and
`Promise`, and rename the `Assume` primitive operation to the more
boring but more explicit `ApplyContract`.
* Formatting
* Add context completion
* Review comments
* Use either record completion or env completion, but not both
* Add test case for env completion
* Fix compilation
* First pass on testing snippets in `manual/syntax.md`
* Remove explicit `TestCase`
* Remove explicit panic
* Add test annotations to the manual
* Stop filtering markdown files
* Update `typing.md` example
* Apply suggestions from code review
Co-authored-by: jneem <joeneeman@gmail.com>
* Some tweaks to multi line string examples
* Move from `nickel-...` info strings to `nickel #...`
---------
Co-authored-by: jneem <joeneeman@gmail.com>
* Removed explicit state from Traverse trait
* Make clippy happy
* Consistent whitespace between documented items
I kept running into this while going through the codebase,
so I thought I'd fix it once and for all.
And no, I did not do this by hand. So I might have missed some cases.
* More formatting.
Mainly includes wrapping of comments to the 100 column mark,
as well as some more formatting on macros and strings.
* restore try_map_state in Traverse impl
* Removed IdentKind
It was technically only used in the PartialEq implmentation of Thunk.
Still, I don't think that had any effect.
* Fix doc comment
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@gmail.com>
---------
Co-authored-by: Taeer Bar-Yam <taeer.bar-yam@tweag.io>
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@gmail.com>
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
* Collect types into a table
* Type-based completion
This also adds a feature flag for turning off the old completer.
* Remove bogus file
* Explicitly visit type annotations
* Add a test for annotated types
* Only do one linearization traversal
* Fix docs, and avoid some clones
* Combine, and resolve metadata
* Add a test
* Slight improvements to the lsp spec
* Refactor
* Remove commented-out code
* Remove the confusing initial-env thing
* Complete the refactor, and document a little better
* Fix some rebase issues
* Clean up some unused code
* Remove obsolete doc
* Review comments
* Fix an off-by-one error in the LSP formatter
According to [the LSP specification](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#range)
the end of a text range in the protocol is exclusive. When executing
a formatting request in the language server we want to replace the
entire document with the formatted result, including any trailing
newlines. This means we need to specify the beginning of the line after
the very last line in the document as the end of the range of text to
be replaced.
This also fixes an annoying behaviour when formatting with NLS in Helix.
Previously, Helix would insist on selecting (what looked like) the
entire document on every formatting request. With this change, Helix
refrains from doing this.
* Update LSP snapshot test
* Prevent unused import warnings when building without `doc`
* Put embedded topiary formatting behind a feature flag for NLS, as well
* Stop sending a formatting edit if nothing changed
Recursive priorites were added pre-RFC005, where their semantics was
straightforward. Because metadata could appear anywhere, recursive
priorities (or also called push priorities) just amounted to have a
primop that pushed the priorities down a term, in one lazy step.
Since RFC005, this isn't possible anymore, because only record field can
hold metadata. It's now much more intricate to implement, because when
encountering a `rec force` at the field level, we first need to know if
there's any value able to receive it underneath this field to know if we
should attach it to the field or no. To know that, we might need to
evaluate the field first, and then decide.
Before sorting out both the new semantics and implementation, this
commit disable the syntax (but keep the rest of the machinery) from
1.2.0 so that we can do some design before shipping new recursive
priorities or scraping them entirely. Recursive priorities were
undocumented, and should have been disabled from 1.0.0, so it's not
considered a breaking change.
* Use `try_str_chunk_as_static_str` instead of duplicating the logic
* Simplify `merge_fields`
* Statically merge piecewise record definitions
* Replicate the behaviour of `eval::merge::merge_fields` more closely
* Fix LSP not showing hover information
After the bidirectional refactoring (better separating the rules between
`infer` and `check`), the LSP was experiencing regressions, not showing
hover information in some cases, in particular within statically typed
blocks.
It turns out the separation between `infer` and `check` makes less clear
which function is responsible for adding the term to the linearizer:
sometimes it's `check`, sometimes it's `infer`, and it really depends on
the call graph and where each function is called from.
It turns out the previous implementation was adding many terms in
double, and this caused the initial regression observed.
Morever, fixing is made hard by the fact that `infer` now doesn't have a
type to provide right now for the linearizer: it first need to, well,
infer it. But the linearizer currently relies on AST nodes being visited
in order, so we can't either call to it whenever we want.
The situation seemed intricate enough that it was easier to separate
"visiting the term" from "amending the type of the term". This commit
thus adds a `retype` method to the `Linearizer` trait, plus some
id-related signature changes. Now, the typechecking code can add a term
to the linearizer as soon as it visits it, and set the type later. More
discipline has been introduced so that `check` and `infer` don't repeat
the same term visits anymore.
Doing so, this commit also cleans a bit the LSP implementation which was
very hard to change getting it right: `IdGen` in particular is gone
(which was maintaining a counter by hand in parallel to the
linearization's size, which was very error-prone, and if any mismatch
occurred, anything could happen). The truth is, the refactor should be
much more involved to make the code maintainable, but this commit is
just a fix for the 1.2.0 release to get out, and the linearizer is a
legacy component that will be scraped soon when the AST-based LSP will
reach feature parity with the linearizer.
* Add Hover capability to tests
* Add regression test for hover after bidir pull request
* Formatting and code clean-up
* Apply suggestions from code review
Co-authored-by: Viktor Kleen <viktor.kleen@tweag.io>
* Make retype calls less verbose
* Fix documentation dangling link
---------
Co-authored-by: Viktor Kleen <viktor.kleen@tweag.io>
* cache most of the work even if rev changes
* longer string for more reliable search.
* more recognizable dummyRev
* nickel-lang-static needs env
* appease nixpkgs-fmt
* copy meta to new derivation
* add comment
* Fix a typo in the release workflow
This changes `os.matrix` into the correct `matrix.os`.
* Use `nodeRuntimes` as required by nixpkgs master, now
* Add nix settings to github-runner.nix
* Disable diffutils tests on arm64 musl
* Add dependencies on `start-runner` in `release-artifacts.yaml`
* Use `--log-format raw-with-logs` like in the CI workflow
* Use the correct cargo package for `nickel-static`
* Adjust linker flags on arm64 musl
* Add github cli and docker to `github-runner.nix`
* Combine static binary and docker image building jobs for caching
* Allow docker access for github jobs
* Use `docker buildx` to assemble the multiplatform image
Allows to `nix run github:tweag/nickel#...` to work as expected
with all packages as well as `pkgs.lib.getExe` returning proper paths.
Also switch to `getExe` with nickel packages in flake.nix
to demonstrate how nice it looks.
* display icon for nickel file in vscode explorer
* implemented with DynAccess.
* added tests.
* Update grammar.lalrpop
move implementation inside CurriedOp
---------
Co-authored-by: Ben Yang <ben@ya.ng>
We previously just reported the error and then pretended to exit
successfully. With this change the process returns `ExitCode::FAILURE`
whenever it needed to report an error, and `ExitCode::SUCCESS`
otherwise.
Fixes#1575
* Add infrastructure for on-demand ARM64 runners on AWS
With this change, ARM64 release artifacts will be built automatically by
a GitHub workflow. Since GitHub doesn't offer hosted runners running on
ARM64, we're spinning up an EC2 spot instance on demand and run the jobs
building ARM64 artifacts there.
As a fun side note, the Terraform infrastructure code is written
entirely in Nickel.
* Remove unused `update-github` script
* Address comments from code review
* Address comments from code review
* Revert "[Fix] Fix bad lexing of mutline string closing delimiter (#1435)"
This reverts commit 664c397aad.
After more investigation, it turns out the original change made it very
annoying to interpolate something between double quotes, because it
conflicts with the multiline string end delimiter:
m%" "%{hello}" "%
After the reverted change, this wouldn't parse correctly anymore. One
can escape the first quote, but it's verbose and harder to read:
m%" %{"\""}%{hello}" "%
Although, we can't see any case where an interpolation sequence with a
heading quotes would have a valid meaning in the reverted commit's
model: it's always an error (applying a string to something). Thus, if
there's a sequence `"%{` in a string, there is no other meaningful
interpretation than this is a quote followed by an interpolation
sequence.
We thus decided to revert this change, although it derives a bit from
the most simple interpretation of parsing multiline string.
* Post-revert fixup: restore some comments and renamings
* Document multiline string parsing special case
* Update core/src/parser/lexer.rs
Co-authored-by: jneem <joeneeman@gmail.com>
* Fix interpolation sequence in pretty printer
---------
Co-authored-by: jneem <joeneeman@gmail.com>
* Render documentation as markdown in LSP
* Use unindent crate to retain code indentation
* Render contracts seperate from documentation
* Remove usages of unindent
* Remove unindent from `Cargo.lock`
---------
Co-authored-by: BuildTools <DeoTimeTheGithubUser@users.noreply.github.com>
Upon the failure of a higher-order contracts, we used to include quite
generic notes showing a plain illustration of the kind of higher-order
violation that happened. However, this text was totally generic (the
example didn't relate to the source code at all), quite verbose (around
4-5 lines of notes), and to be honest, not very helpful.
We now have good mechanisms to underline the right part of the function
contract that failed, together with customized label (e.g. "broken by the
caller"), which makes look like the original generic note aren't very
valuable.
This patch ditches those notes altogether.
* Import completion
* Use `cache::normalize_path` instead of `fs::canonicalize`
* Add cached files as candidates for import autocompletion
* Rename `InputFormat::from_path_buf` to `InputFormat::from_path`
* Deduplication between server cached files and disk files
---------
Co-authored-by: deotime <89555032+DeoTimeTheGithubUser@users.noreply.github.com>
In an attempt to free the allocation of the constraints of a record row
unification variable that is being assigned to some record rows, the
code checking that row constraints are satisfied was removing the
constraints from the global state. Since rows are defined as linked
list, if the constraint wasn't violated on the first row, this function
would recursively call itself. But then the subsequent recursive calls
would try to get the constraints from the state again, to only find an
empty set constraints, as it has been removed just before. The function
thus wouldn't detect constraint violations happening in the tail of the
record rows.
This patch defines a subfunction which passes the initial constraints
along recursive calls, such that they aren't lost during recursion,
instead of trying to get them from the state again at each recursive
call.
* set arguments with --
Create term that merges command line arguments with program
* Move building the override term into `Program`
* instead of immediately evaluating argument values, use
`ImportResolver::add_string` to make them separate imports.
* Move CLI export into its own file
* Integrate record builder interface
* Make record field paths work correctly
* Evaluate annotations, too, for record normal form
* Make term interfaces a first class concept
* Stop printing terms on export
* Rename eval_for_doc to be less doc-specific
And expand the documentation at the same time.
* Augment FieldInterface with more data
Augment the field interface type - for freeform argument passing in the
CLI - with additional metadata, such as being optional or defined, taken
directly from the original field's metadata. Add a somehow heuristic
(but simple) `is_input` method, which decides if a field is an input and
should have a dedicated argument.
Minor reworking/renaming of other part of the CLI export code around
freeform arguments.
* Restore the path argument, add more documentation
* Use Field/FieldMetadata instead of custom types
In the CLI export function, instead of using a structure that mostly
mirror record fields, we directly use record fields to avoid code
duplication, although fields do carry a bit more information that what
we exactly need.
* Use query printer to render freeform args help
* Continue proper handling of overrides/inputs in CLI
* Fix eval_record_spine, add sources for CLI arguments
* Remove debug println, improve CLI freeform output
* Move around reporting code to error module
* Actually implement --override, add custom error messages
* Make overrides have a `force` priority
* Add some untested tests
* Small rewording of Ident documentation
* Post-rebase fixups + get rid of Merge trait
* Fix snapshot test runner for freeform args
* Fix CLI freeform snapshot tests
* Fix unused import warning
* Formatting
* Review pass, smallfixes and clippy fix
* Fix cargo doc warnings
* Fix 1.72 new clippy warnings
* Update snapshots after extra-args -> customize mode
* Move the Combine trait in its own mod
* Apply suggestions from code review
Co-authored-by: Viktor Kleen <viktor.kleen@tweag.io>
* Update core/src/term/make/builder.rs
Co-authored-by: Viktor Kleen <viktor.kleen@tweag.io>
* Remove questionable Option<> layer
* Update cli/src/export.rs
Co-authored-by: Viktor Kleen <viktor.kleen@tweag.io>
* Update cli/src/export.rs
Co-authored-by: jneem <joeneeman@gmail.com>
* Apply suggestions from code review
Co-authored-by: jneem <joeneeman@gmail.com>
* Add warning about usage of Label::default
---------
Co-authored-by: Yann Hamdaoui <yann.hamdaoui@tweag.io>
Co-authored-by: Viktor Kleen <viktor.kleen@tweag.io>
Co-authored-by: jneem <joeneeman@gmail.com>
* Add multiline string support for VSCode autoclosing pairs
* Support up to 4 % symbols
---------
Co-authored-by: BuildTools <DeoTimeTheGithubUser@users.noreply.github.com>
This fixes an off-by-one error in the handling of incomplete input.
It also makes import resolution in incomplete input more reliable --
previously it would only work when the file being opened is in the
current working directory.
