Remove dependency on fstar's Getopt#150
Merged
Merged
Conversation
Coding against internal modules of the F* compiler is not maintainable, and there is no need to do so here. With the new build, fstar-lib will not even include this module (although maybe it could eventually), so this is also more future-proof.
Member
Author
|
cc @nikswamy , any opinion here? I will probably also mess with F*'s getopt soon-ish. |
tahina-pro
enabled auto-merge
October 23, 2024 19:48
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a follow up to #148.
Coding against internal modules of the F* compiler is not maintainable,
and there is no need to do so here. With the new build, fstar-lib will
not even include this module (although maybe it could eventually), so
this is also more future-proof.