Skip to content

Conversation

@kape1395
Copy link
Collaborator

No description provided.

@kape1395 kape1395 self-assigned this Sep 15, 2024
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
@ahelwer
Copy link
Collaborator

ahelwer commented Dec 4, 2024

@kape1395 Is the idea we would publish TLAPM as a package to OPAM? Do you think it would be a good idea to split off the parser into its own package, since that is probably the only thing people would want to consume?

@kape1395
Copy link
Collaborator Author

kape1395 commented Dec 5, 2024

That would be useful, but that's probably not only the parser.
For example, it was an attempt to use the lib as a TLA+ formatter.

I once tried to make it publishable via OPAM, but the build failed when performed in OPAM while succeeding from the source directly. Something has to be double-checked.

@ahelwer
Copy link
Collaborator

ahelwer commented Dec 5, 2024

I think it might not make sense to publish all of TLAPM as an OPAM package, but things like the parser - which could be used in other projects, like a formatter - would make sense. I'll keep the idea of separating the parser out into its own source directory in the back of my mind, I'll be writing a lot of tests for it in the future.

With regard to these changes, what would you say their objective is?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants