-
-
Notifications
You must be signed in to change notification settings - Fork 568
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
prime_range should allow a step #29760
Comments
This comment has been minimized.
This comment has been minimized.
comment:1
Upon further reflection, maybe I should also be asking for this in the |
comment:2
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
Branch: u/roed/prime_range |
comment:4
Dependence on #31548 is in order to have FLINT's Last 10 new commits:
|
Author: David Roe |
Commit: |
Dependencies: #31548 |
comment:5
The changes in this ticket are all in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Looks fine modulo the dependence on #31548. |
comment:8
Setting a new milestone for this ticket based on a cursory review. |
comment:9
needs rebase, dependency too |
Is there any reason not to implement the following?
For this ticket, I have in mind the easy fix of running the same internal algorithm and retaining only the answers in the desired congruence class; that is,
prime_range(x, y, z)
would be equivalent toA more advanced (and more efficient) version would be to change the underlying algorithm.
Depends on #31548
CC: @DaveWitteMorris
Component: number theory
Author: David Roe
Branch/Commit: u/roed/prime_range @
7f0a385
Issue created by migration from https://trac.sagemath.org/ticket/29760
The text was updated successfully, but these errors were encountered: