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

fix(contracts): minor changes to fix compilation warnings #134

Merged

Conversation

AugustoL
Copy link
Member

No description provided.

@AugustoL
Copy link
Member Author

The only compilation warnings lefts are the ones form the VotingMacineCallbacks from daostack contracts that we dont want to change them yet.

@@ -412,7 +412,7 @@ contract WalletScheme {
function mintReputation(
uint256 _amount,
address _beneficiary,
bytes32 _proposalId
bytes32
Copy link
Member

Choose a reason for hiding this comment

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

Hey! This is a question for me to understand better about unnamed parameters.
Since in this case you are not overriding other function, why is it that you are including it?

Copy link
Member Author

Choose a reason for hiding this comment

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

because in the VotingmachineCallbacks that we are extending it always passes the proposalId, but im not using it, in fact I think no scheme is using it but it was defined like that when it was written years ago.

So I just remove the parameter name and I leave it empty, this way the function signature will be the same as it uses three params, but im only using two.

Bad practice, but wel..thats what we get from supporting this legacy contracts

Copy link
Member

Choose a reason for hiding this comment

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

Got it. Thanks!

@AugustoL AugustoL merged commit 5905d1a into DXgovernance:develop Apr 27, 2022
@AugustoL AugustoL deleted the fix/dxvote-compilation-warnings branch April 27, 2022 15:59
@AugustoL AugustoL mentioned this pull request May 5, 2022
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.

None yet

3 participants