Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

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

Search

Clear

Search syntax tips

Provide feedback

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

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

huonw / primal Public

Notifications You must be signed in to change notification settings
Fork 18
Star 114

Code
Issues 6
Pull requests 3
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

sieve: Use `saturating_add` when computing `next_base`#61

Merged

cuviper merged 6 commits intohuonw:masterhuonw/primal:masterfrom cuviper:saturating-next_basecuviper/primal:saturating-next_baseCopy head branch name to clipboard

Jun 7, 2024

+28-37

Conversation Commits6 (6)Checks Files changed

Commits

Commits on Jun 7, 2024

sieve: Use saturating_add when computing next_base
cuviper
committed
Run all CI on pull requests
cuviper
committed
bors is dead
cuviper
committed
Use s390x for big-endian testing
cuviper
committed
Upgrade to actions/checkout@v4
cuviper
committed
Add a "bors" summary status
cuviper
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.