8000 Remove the hypnaming API from Evarutil. by ppedrot · Pull Request #20689 · rocq-prover/rocq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remove the hypnaming API from Evarutil. #20689

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

Merged
merged 1 commit into from
Jun 4, 2025

Conversation

ppedrot
Copy link
Member
@ppedrot ppedrot commented May 28, 2025

All callers where behaving as if it were RenameExistingBut, hence only the varset matters.

All callers where behaving as if it where RenameExistingBut, hence only
the varset matters.
@ppedrot ppedrot added this to the 9.1+rc1 milestone May 28, 2025
@ppedrot ppedrot requested review from a team as code owners May 28, 2025 15:28
@ppedrot ppedrot added kind: cleanup Code removal, deprecation, refactorings, etc. request: full CI Use this label when you want your next push to trigger a full CI. labels May 28, 2025
@coqbot-app coqbot-app bot removed the request: full CI Use this label when you want your next push to trigger a full CI. label May 28, 2025
| RenameExistingBut of VarSet.t
| FailIfConflict
| ProgramNaming of VarSet.t
type naming_mode = VarSet.t
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe keep the constructor? ie

Suggested change
type naming_mode = VarSet.t
type naming_mode = RenameExistingBut of VarSet.t

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But its name is now completely misleading. I don't mind keeping a box somewhere but the inductive approach doesn't look right to me. Since we never pattern-match on this from the outside we could add it as abstract injections, but then I don't really see the added value compared to just VarSet.t.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it misleading?

Anyway transparent type aliases aren't great either, why even have it instead of using varset directly?

@SkySkimmer SkySkimmer self-assigned this May 28, 2025
Copy link
Contributor
@SkySkimmer SkySkimmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's forget about my type alias nitpick

@SkySkimmer
Copy link
Contributor

@coqbot merge now

@coqbot-app coqbot-app bot merged commit b08c32b into rocq-prover:master Jun 4, 2025
7 checks passed
@ppedrot ppedrot deleted the rm-hypnaming-api branch June 4, 2025 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: cleanup Code removal, deprecation, refactorings, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0