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
There are many extension methods in use by the neo project.
I would like the group them up into individual static classes based on their type. During this process I would also comment the extension methods to explain what they are doing. This will improve the codebase for future development and documentation.
/// <summary>/// Divides the value of the source BigInteger by the division parameter, and returns the remainder./// See: https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/modulus-operator/// </summary>internalstatic BigInteger Mod(thisBigIntegersource,BigIntegerdivision){source %= division;if(source.Sign <0)source+=division;returnsource;}
The text was updated successfully, but these errors were encountered:
@jeremylcarter these would be useful improvements. We (City of Zion) have improvements of this nature planned for the core, please could you drop into #develop in slack and DM 'ashant' so we can coordinate?
Its a great idea but I don't see anyone else trying to improve the quality of incoming code. Why would I slave away at cleaning up the code, documenting it and making it readable when incoming code from other contributors has no comments, does not follow conventions and will require a clean up again. Its a never ending cycle.
There are many extension methods in use by the neo project.
I would like the group them up into individual static classes based on their type. During this process I would also comment the extension methods to explain what they are doing. This will improve the codebase for future development and documentation.
For example:
Would become
The text was updated successfully, but these errors were encountered: