Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tactics: exposing ext_options/all_ext_options #3034

Merged
merged 6 commits into from
Aug 25, 2023

Conversation

mtzguido
Copy link
Member

cc @nikswamy, there's no way to access them from tactics otherwise as of yet, right?

Also I wonder if it would be more future proof to provide a KV interface, such as:

val get_ext : key:string -> string

And writing --ext k=v to define one. The key could use dots to separate namespaces purely as a convention. We could maybe define an ext_options analogue that looks at the prefix of each key to decide which pairs to return.

@mtzguido
Copy link
Member Author

Updated this PR to implement the KV semantics.

@mtzguido mtzguido enabled auto-merge August 25, 2023 15:00
@mtzguido mtzguido merged commit ca5dbb6 into FStarLang:master Aug 25, 2023
@mtzguido mtzguido deleted the tac-ext-opts branch August 25, 2023 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant