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 obsolete functionality #5943

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fingolfin
Copy link
Member

Most of this was commented out for an extended period of time. A few things weren't but simply are not in use by any distributed package anymore.

Specifically, the following are removed:

  • ReadPkg
  • TemporaryGlobalVarName
  • R_N
  • R_X
  • AdditiveInverseAttr
  • AdditiveInverseSM
  • InverseAttr
  • InverseSM
  • OneAttr
  • OneSM
  • TransposedMatAttr
  • ZeroAttr
  • ZeroSM
  • AINV
  • INV_MUT
  • ONE_MUT
  • ZERO

All of these have been deprecated since at least December 2022.

Most of this was commented out for an extended period of time. A
few things weren't but simply are not in use by any distributed
package anymore.
@fingolfin fingolfin added topic: library release notes: use title For PRs: the title of this PR is suitable for direct use in the release notes kind: removal or deprecation A feature was removed or deprecated / made obsolete labels Feb 18, 2025
Copy link
Contributor

@ThomasBreuer ThomasBreuer left a comment

Choose a reason for hiding this comment

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

I am not sure what is the best way to deal with deprecated names and code.

There is a manual chapter about Replaced and Removed Command Names which documents deprecations, name changes, removed code since the time of the switch from GAP 3 to GAP 4.

If we keep this kind of documentation up to date then one can in principle find out what one should do if one has problems with some old GAP code.

On the other hand, the easiest way to understand what exactly the removed code has done is to look at this code, which is difficult if the code is no longer available.

Moreover, there is the danger that a variable name got deprecated and removed, and after some time this name is chosen (by chance) for something new, perhaps in a package, and then old code that uses the variable with that name might even not notice that there is a problem. In this sense, it would be safer to keep the deprecated names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: removal or deprecation A feature was removed or deprecated / made obsolete release notes: use title For PRs: the title of this PR is suitable for direct use in the release notes topic: library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants