Replies: 1 comment
-
Yeah, why not I suppose. If you think our Loc type is good enough for your use cases, we can extract it into a separate package. I think you'll need to lead the effort on that though. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am extracting here the part of this discussion ocaml/opam-repository#26604 about releasing a loc package to opam, as it relates to dune:
I am using a type to represent a range of lexing positions from a file, which I called Loc.t. It's here.
I use it as dependency to decorate AST nodes built by parsers, enabling located error messages during file processing (compilers, interpreters, linters, refactor tools, etc.).
I am considering submitting it to the opam-repository, but I have some reservations.
It is very similar to Dune's
Stdune.Loc
module (and actually usesstdune
under the hood).Perhaps it would make more sense to work on extracting the Dune one as a foundational package (such as pp, dyn, and ordering), rather than maintaining this one separately.
Would you have interest in entertaining such extraction, and make what's currently
Stdune.Loc
a standalone & reusable package?Beta Was this translation helpful? Give feedback.
All reactions