Update ERC-20 walk-through for Solidity 0.8.0+ and SafeMath context #14909
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Addresses outdated explanations in the ERC-20 contract walk-through to align with modern Solidity practices: Constructor Visibility: Added a comment clarifying that `public` is implicit in Solidity ≥0.7.0. SafeMath Clarification: Updated the SafeMath library explanation to reflect that it is unnecessary in Solidity ≥0.8.0 due to built-in overflow checks.
M3dython
requested review from
wackerow,
corwintines,
pettinarip and
minimalsm
as code owners
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses outdated explanations in the ERC-20 contract walk-through to align with modern Solidity practices:
publicis implicit in Solidity ≥0.7.0.These changes ensure the documentation accurately reflects current best practices and avoids confusion for developers using newer Solidity versions.