Skip to content

Point release of v2.4 that supports agda-2.9 - #3126

Draft
Taneb wants to merge 6 commits into
v2.4-releasefrom
v2.4-dev
Draft

Taneb wants to merge 6 commits into
v2.4-releasefrom
v2.4-dev

Conversation

@Taneb

@Taneb Taneb commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

I'm not sure that this PR should be merged at all, rather than a tag be made out of its branch

This build with Agda 2.9-rc1.

andreasabel and others added 4 commits October 19, 2026 16:53
Addresses these two issues:
1. A non-operator `Agda.Builtin.Int.pos` is imported as prefix operator `+_` without giving it an explicit fixity declaration.
2. Some non-operators are given a fixity where it does not make sense.

Both issues are just of cosmetic nature atm, but may change to become issues in the future, see agda/agda#1438 .

It seems best to address these issues now.
Note that the syntax addressing issue 1 has been available since Agda 2.6.1 already.

Closes #3114.
These are implemented with a sneaky irrelelvant projection that agda 2.9 prevents, and are surprisingly unused or replaceable
@Taneb Taneb changed the title V2.4 dev Point release of v2.4 that supports agda-2.9 Oct 19, 2026
@jamesmckinna

Copy link
Copy Markdown
Collaborator

Did you intend to merge this into the release-v2.4 branch?

@Taneb

Taneb commented Oct 19, 2026

Copy link
Copy Markdown
Member Author

Did you intend to merge this into the release-v2.4 branch?

Yes, or at least, I intended to base the PR off the v2.4-release branch, because that's the branch that reflects the 2.4 release, from which this is supposed to be a small change.

@gallais
gallais marked this pull request as ready for review October 29, 2026 16:02
@gallais
gallais marked this pull request as draft October 29, 2026 16:03
@gallais

gallais commented Oct 29, 2026

Copy link
Copy Markdown
Member

CI works!

@MatthewDaggitt

Copy link
Copy Markdown
Collaborator

Yup, this is how I've done it in the past. The -release branches just get updated as new versions of Agda gets put out, and then we tag the new library releases on the updated -release branch. I vote for merging.

This branch has not been deployed

No deployments
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.

5 participants