Skip to content

Remove unused "PC STACK" variables for from the left collectors (this breaks compatibility with polycyclic version 2.16 and older; use 2.17 or newer instead)#6191

Merged
fingolfin merged 5 commits intogap-system:masterfrom
stertooy:remove-pc-stack-vars
Jan 19, 2026

Conversation

@stertooy
Copy link
Copy Markdown
Contributor

@stertooy stertooy commented Jan 11, 2026

Some minor cleanup. Removes unused variables that were originally used by Polycyclic (see gap-packages/polycyclic#6).

Text for release notes

Removed some variables that were previously used by the Polycyclic package. This breaks compatibility with Polycyclic versions 2.16 and older, upgrading to version 2.17 or newer is required to use this package.

Further details

This breaks compatibility with older versions of Polycyclic (i.e. 2.16 and older). Latest version (2.17) works fine.

@ChrisJefferson
Copy link
Copy Markdown
Contributor

This is definitely a PR we want to merge at some point, the only question is if we should merge it now, or leave it open and give people a little bit longer to upgrade.

@fingolfin
Copy link
Copy Markdown
Member

Then we should it do the GAPInfo.PackagesRestrictions record in the GAP library, which lists for several packages minimal required versions.

@stertooy
Copy link
Copy Markdown
Contributor Author

This is definitely a PR we want to merge at some point, the only question is if we should merge it now, or leave it open and give people a little bit longer to upgrade.

There's certainly no rush in merging this. Though, given the number of bug fixes in Polycyclic 2.17, I don't think pushing users to upgrade is necessarily a bad thing.

A possible middle ground is to leave in the line

AssConstantGVar(GVarName("NO_STACKS_INSIDE_COLLECTORS"), True);

Then Polycyclic 2.15, 2.15.1 and 2.16 will produce Syntax Warnings when loaded, but they will actually work fine.

Then we should it do the GAPInfo.PackagesRestrictions record in the GAP library, which lists for several packages minimal required versions.

Added to the PR :)

@fingolfin
Copy link
Copy Markdown
Member

OK, it's fine to me as it is, with the warning, and for GAP 4.16.0.

But I suggest we put this into the release note then, with a suitable text informing users (for most it won't matter, but if someone runs into the error, then they can at least in principle find it in the NEWS)

@fingolfin fingolfin added topic: packages issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker) topic: kernel release notes: use title For PRs: the title of this PR is suitable for direct use in the release notes labels Jan 19, 2026
@fingolfin fingolfin changed the title Remove unused PC STACK variables for from the left collectors Remove unused "PC STACK" variables for from the left collectors (this breaks compatibility with polycyclic version 2.16 and older; use 2.17 or newer instead) Jan 19, 2026
@fingolfin fingolfin merged commit 384ceeb into gap-system:master Jan 19, 2026
32 checks passed
@stertooy stertooy deleted the remove-pc-stack-vars branch February 12, 2026 17:13
hulpke pushed a commit to hulpke/gap that referenced this pull request Feb 19, 2026
… breaks compatibility with polycyclic version 2.16 and older; use 2.17 or newer instead) (gap-system#6191)
cdwensley pushed a commit to cdwensley/gap that referenced this pull request Feb 26, 2026
… breaks compatibility with polycyclic version 2.16 and older; use 2.17 or newer instead) (gap-system#6191)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release notes: use title For PRs: the title of this PR is suitable for direct use in the release notes topic: kernel topic: packages issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants