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

Remove FStar.Ghost.Pull #3636

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Remove FStar.Ghost.Pull #3636

wants to merge 2 commits into from

Conversation

gebner
Copy link
Contributor

@gebner gebner commented Dec 17, 2024

No description provided.

@TWal
Copy link
Contributor

TWal commented Dec 17, 2024

I am curious why this axiom is removed? Is it because it introduces an unsoundness?

@gebner
Copy link
Contributor Author

gebner commented Dec 17, 2024

Hi Theophile. There are no concrete plans to pull pull. That's why this PR is marked as draft.

However, pull is one of the few axioms that we include in F* and I have been trying to figure out how much code relies on it. So far I couldn't find anything that makes essential use of pull (see also FStarLang/pulse#291 and project-everest/everparse#160). If you use pull, I'd be curious to learn more.

Is it because it introduces an unsoundness?

I believe that pull is sound. But the negation of pull piqued my interest.

@TWal
Copy link
Contributor

TWal commented Dec 18, 2024

If you use pull, I'd be curious to learn more.

No, I am not using the pull axiom.

I see, if I understand correctly this axiom is convenient, but in practice it can be replaced by something else, so this PR asks the question why we should keep it?

@gebner
Copy link
Contributor Author

gebner commented Dec 18, 2024

I see, if I understand correctly this axiom is convenient, but in practice it can be replaced by something else, so this PR asks the question why we should keep it?

Apparently, my comment was too opaque then. 😄 I want to add a parametricity axiom to F* that conflicts with pull. If pull was actually used, then that would be a big price to pay. But as this PR shows, we can easily remove pull and make room for this other axiom.

@TWal
Copy link
Contributor

TWal commented Dec 19, 2024

Ah ok, thanks for the explanations!

@gebner gebner force-pushed the gebner_rm_ghost_pull branch from f738d5c to 77f5528 Compare December 21, 2024 00:49
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.

2 participants