Skip to content

[Style]: Move BigInteger extensions from Utility to BigIntegerExtensions #3916

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

Merged
merged 3 commits into from
May 6, 2025

Conversation

Wi1l-B0t
Copy link
Contributor

@Wi1l-B0t Wi1l-B0t commented May 1, 2025

Description

Just move BigInteger extensions from Utility to BigIntegerExtensions.

  • Optimization (the change is only an optimization)
  • Style (the change is only a code style for better maintenance or standard purpose)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

}

[MethodImpl(MethodImplOptions.AggressiveInlining)]
private static int BitCount(byte w)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BitCount has changed, this should be done in a different pr

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, Submit this simpified implementation later.

@Wi1l-B0t Wi1l-B0t force-pushed the style.move-bigint-extensions branch from 7412acf to becb238 Compare May 2, 2025 07:51
@shargon
Copy link
Member

shargon commented May 4, 2025

Why coverage decresed?

@shargon shargon merged commit e53a894 into neo-project:master May 6, 2025
6 of 7 checks passed
NGDAdmin pushed a commit that referenced this pull request May 6, 2025
* optimize: show native contract net active yet

* Update src/Neo.CLI/CLI/MainService.Native.cs

* style: move BigInteger extensions from Utility to BigIntegerExtensions (#3916)

---------

Co-authored-by: Shargon <[email protected]>
@Wi1l-B0t Wi1l-B0t deleted the style.move-bigint-extensions branch May 7, 2025 14:16
@Wi1l-B0t Wi1l-B0t mentioned this pull request May 7, 2025
14 tasks
shargon added a commit that referenced this pull request May 12, 2025
* [`Optimize`]: show native contract is active or not (#3922)

* optimize: show native contract net active yet

* Update src/Neo.CLI/CLI/MainService.Native.cs

* style: move BigInteger extensions from Utility to BigIntegerExtensions (#3916)

---------

Co-authored-by: Shargon <[email protected]>

* Avoid empty snupkg in release (#3925)

* v3.8.1 (#3930)

* Revert workflow branch

---------

Co-authored-by: Will <[email protected]>
Co-authored-by: Shargon <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants