Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Bug in range sieve when left boundry is 0#1471

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
nartherion wants to merge1 commit intocp-algorithms:main
base:main
Choose a base branch
Loading
fromnartherion:sieve-bug

Conversation

nartherion
Copy link

In case whenL = 0 andR > 0, algorithm will return 0 and 1 as primes.

In case when `L = 0` and `R > 0`, algorithm will say that 0 and 1 are primes.Index initialization improvement
@mhayter
Copy link
Contributor

It's true. That 0 as left boundary does label 0 and 1 as primes I'm suspicious of the changing of bounds. Has your code been tested on problems elsewhere? We probably should write some tests to make sure this works and will work in the future.

@mhaytermhayter added the bug labelJun 21, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@nartherion@mhayter

[8]ページ先頭

©2009-2025 Movatter.jp