Closed shargon closed 8 months ago
Totals | |
---|---|
Change from base Build 3779439269: | 0.04% |
Covered Lines: | 2034 |
Relevant Lines: | 2428 |
The Your code is supported in dotnet
standard. Please check the #6 and download it or you try converting to 'netstandard2.1
. You will find that that the interfaces are the problem. Not static methods, only interfaces can't have static methods. Tons more code was changed than just static methods. I dont see it being a problem or a performance issue. This library is only used in ApplicationEngine
for the syscalls
. Plus ApplicationEngine
uses tons of reflection to call syscall
The Your code is supported in
dotnet
standard. Please check the #6 and download it or you try converting to'netstandard2.1
. You will find that that the interfaces are the problem. Not static methods, only interfaces can't have static methods. Tons more code was changed than just static methods. I dont see it being a problem or a performance issue. This library is only used inApplicationEngine
for thesyscalls
. PlusApplicationEngine
uses tons of reflection to callsyscall
That's why I want to remove the static methods in the interface.
Closed in favor of https://github.com/neo-project/Neo.Cryptography.BLS12_381/pull/11
In order to improve the dotnet standard migration and reduce the risk changes, I want to remove the static methods one by one
In this PR:
INumber.Size