Fix loc after file resolution #242
Merged
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
gares
force-pushed
the
fix-loc-after-file-resolution
branch
from
09301af to
b5fae2c
Compare
|
Cannot find the branch: |
|
What command should I write to get it, I did git remote update, but still not found |
|
|
This reverts commit b5fae2c.
Fix loc after file resolution2
|
I like the approach, **** dune! |
|
elpi already depends on |
Remove deps on Str (use Re.Str instead)
gares
commented
Jul 11, 2024
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.
@FissoreD would you mind testing this version of Elpi? It should give (in coq-elpi) better file names in error messages