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

Varieties v0.3 #3567

Open
wants to merge 206 commits into
base: development
Choose a base branch
from
Open

Varieties v0.3 #3567

wants to merge 206 commits into from

Conversation

mahrud
Copy link
Member

@mahrud mahrud commented Nov 1, 2024

This is a repeat of #3517, which is on top of #3522 and shares a exact few commits with #3526, but I don't believe there should be a conflict.

@mahrud mahrud changed the base branch from master to development November 1, 2024 08:10
@mahrud
Copy link
Member Author

mahrud commented Nov 6, 2024

@ggsmith @mikestillman is everyone happy with merging this?

mahrud and others added 26 commits November 22, 2024 03:35
Also changed g \\ f to call quotient'(f, g) instead.
@mahrud
Copy link
Member Author

mahrud commented Nov 22, 2024

It would be good to have this merged soon so the branch is free to continue developing on.

@mahrud
Copy link
Member Author

mahrud commented Dec 4, 2024

@mikestillman @ggsmith should I go ahead and merge this? We shouldn't wait until a week before the next release to merge big pull requests.

@ggsmith
Copy link
Contributor

ggsmith commented Dec 4, 2024

I haven't yet had time to look at the details

@mahrud
Copy link
Member Author

mahrud commented Dec 4, 2024

You had reviewed the previous PR #3517, which I accidentally closed and had to reopen. I think I've addressed all of your comments there. No other changes have been added since.

Do you have an estimate of when you could look at the details? Varieties wasn't updated in version 1.24.05 and again didn't get updated in 1.24.11. There are new features and bug fixes that Devlin and I have worked on, but I'm afraid if we continue it won't make it to 1.25 either.

@mikestillman
Copy link
Member

@mahrud I'm ready to look at your few open PR's. I'm a bit confused about which to do in what order. 3522 first, then 3550, then 3567, then 3582? Are there duplicate commits in these?

@mahrud
Copy link
Member Author

mahrud commented Jan 10, 2025

You can start from the smallest ones if you prefer, but the order they're reviewed or merged doesn't matter.

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.

7 participants