Fix liveness warnings for __findFile #109
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Search paths desugar to calling __findFile in Nix. List parameter is added cause __findFile receives one (with NIXPATH or error thunk). Might be useful for type inference.
|
This currently emits «Undefined name» warnings due to __findFile not being in scope. I probably should modify "generated.expr" generation, however I am not sure how to add primops without the use of tty yet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Search paths desugar to calling __findFile in Nix.
This fixes warnings in
let __findFile = a: b: "hi ${b}!"; in <gilbert>List parameter is added cause __findFile receives one (with NIXPATH or error thunk). Might be useful for type inference.
I am not sure, if accounting for such a hack is in scope of this lsp, but I've seen it being used and I am using it myself.