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

Bump float_next_after from 0.1.5 to 1.0.0 #1

Merged
merged 1 commit into from
Dec 13, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 13, 2022

Bumps float_next_after from 0.1.5 to 1.0.0.

Changelog

Sourced from float_next_after's changelog.

Version 1.0.0

Breaking changes:

  • The NextAfter trait is now provided for the types f32 and f64 and no longer provided as a generic constrained to the type num_traits::Float.
  • The library is now #![no_std].

New Features:

  • Removed dependence on the std library, the library is now #![no_std].
  • Now uses macros to create the trait for f32 and f64 directly without any use of the generic contraint using num_traits::Float.
  • CI/CD test running on git push.

Structural changes:

  • Tests are written with a macro now so no code needs to be repeated to run tests for f32 and f64.
  • Code cleanup with:
    • 0 equality check integrated into short_circuit_operands.
    • Early return is used throughout.
    • Single check for infinite source number (it had been a separate check for positive and for negative infinity).

Performance:

  • Removed one unneccesary creation of a stack variable.

Version 0.7.0

Bug fixes:

  • Updated the examples in README.md
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [float_next_after](https://gitlab.com/bronsonbdevost/next_afterf) from 0.1.5 to 1.0.0.
- [Release notes](https://gitlab.com/bronsonbdevost/next_afterf/tags)
- [Changelog](https://gitlab.com/bronsonbdevost/next_afterf/blob/main/CHANGES.md)
- [Commits](https://gitlab.com/bronsonbdevost/next_afterf/commits/main)

---
updated-dependencies:
- dependency-name: float_next_after
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Dec 13, 2022
@ringsaturn ringsaturn merged commit 5007d84 into main Dec 13, 2022
@ringsaturn ringsaturn deleted the dependabot/cargo/float_next_after-1.0.0 branch December 13, 2022 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file rust Pull requests that update Rust code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant