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
move ZModulo to test suite #17258
move ZModulo to test suite #17258
Conversation
@coqbot run full ci |
elpi failure is also on master 8e03144 |
@andres-erbsen note that the usual policy before removing something is that potential users should have been able to see a deprecation warning for at least two versions. So I'm afraid we cannot remove that now. |
Are you sure this is the policy even for changes with backwards-compatible fixups? The most relevant written record I can find says
(from the dissertation of @Zimmi48, https://hal.inria.fr/tel-02451322v1 page 44) Removals based on similar reasoning have been approved and merged as well, e.g. #15268. |
The fact that we cannot deprecate entire modules is a missing feature that would be very useful here. |
@andres-erbsen indeed I was wrong with the requirement for deprecation in two releases, one can be enough under some circumstances. |
Here is an issue about deprecating libraries #8032 |
The deprecation was announced in the previous release here. For a library that was actually used or understood to be useful, I can see that aiming for a higher level of communication (some solution to #8032, perhaps manual) would have value, but AFAIK this file has only caused confusion so far so I don't think it is worth holding back with its removal any longer. |
@andres-erbsen As it has been deprecated previously, I support you removing this. |
Given that CI reveals no issues, I also support this removal (but it should be documented in a changelog). |
20ac535
to
098ab4c
Compare
2dd8fe9
to
bb11ead
Compare
AFAICT this is ready and needs an assignee. @proux01 maybe? |
Maybe I should clarify my position here: I still think this deserves proper deprecation warnings and I won't merge without them (I would otheriwse) but I will not oppose if anyone else think it's fine without warnings. |
Either we merge this quickly, or we do deprecate the relevant definitions before the 8.18 branch. Since there is not much momentum for the first option, maybe the second should be considered? |
bb11ead
to
120e911
Compare
Now that 8.18 has branched, this can be merged into master, right? |
Gentle ping @coq/number-maintainers |
@coqbot run full ci |
120e911
to
76e6a35
Compare
Full CI failures look unrelated, refman failure is fixed in latest version. |
@coqbot merge now |
@Alizter: You cannot merge this PR because:
|
@coqbot merge now |
#16914