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

[BREAKING] Allow NatSpec comments for state variables. #8749

Merged

Conversation

aarlt
Copy link
Member

@aarlt aarlt commented Apr 22, 2020

See #8532.

This PR will replace some warnings with errors.

@aarlt aarlt force-pushed the structured-docs-variables-aarlt-breaking branch from a1d681d to 2fdcde4 Compare April 23, 2020 20:26
@axic
Copy link
Member

axic commented Apr 27, 2020

Please also see the last comments on #3418.

Copy link
Member

@hrkrshnn hrkrshnn left a comment

Choose a reason for hiding this comment

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

Also needs a rebase. The new solidity-external-tests repos and the target branch will show up in the rebase.

test/externalTests/colony.sh Outdated Show resolved Hide resolved
test/externalTests/zeppelin.sh Outdated Show resolved Hide resolved
test/libsolidity/SolidityNatspecJSON.cpp Outdated Show resolved Hide resolved
test/libsolidity/SolidityNatspecJSON.cpp Outdated Show resolved Hide resolved
@aarlt aarlt marked this pull request as draft May 11, 2020 18:40
@aarlt aarlt force-pushed the structured-docs-variables-aarlt-breaking branch 6 times, most recently from 904875a to e7aa7fb Compare May 20, 2020 18:21
@@ -254,7 +254,7 @@ BOOST_AUTO_TEST_CASE(natspec_comment_in_function_body)
/// fun1 description
function fun1(uint256 a) {
var b;
/// I should not interfere with actual natspec comments
// I should not interfere with actual natspec comments (natspec comments on local variables not allowed anymore)
Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe we should remove the comments?

Copy link
Member

Choose a reason for hiding this comment

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

Maybe then we should have tests that do interfere with actual natspec comments? (or do we already have those?)

Copy link
Member

Choose a reason for hiding this comment

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

@aarlt do we have tests like my previous comment?

Copy link
Member Author

Choose a reason for hiding this comment

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

@leonardoalt at least here there will be no interference possible, because it is just forbidden now on local variables. But maybe we can add some natspecs to other expressions within a function body, I'm not sure whether it will make sense. However, I will check that.

Copy link
Member

Choose a reason for hiding this comment

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

Ah right

@aarlt aarlt marked this pull request as ready for review May 20, 2020 20:33
@aarlt aarlt force-pushed the structured-docs-variables-aarlt-breaking branch 2 times, most recently from ff6b2d0 to bbab19c Compare May 25, 2020 11:13
- changing some warnings to errors
@aarlt aarlt force-pushed the structured-docs-variables-aarlt-breaking branch from bbab19c to cb5bfc7 Compare May 26, 2020 16:20
@chriseth chriseth merged commit b4c6fdb into ethereum:breaking Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants