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

“Consider using 'transfer' in place of 'call.value()” is a false error message #280

Open
avatar-lavventura opened this issue Jan 13, 2020 · 1 comment

Comments

@avatar-lavventura
Copy link

avatar-lavventura commented Jan 13, 2020

Consider using 'transfer' in place of 'call.value()'.                                                                                                                                 security/no-call-value

As for the solidity version 0.6.0, it is recommended to use call.value() from now on and using transfer is not recommended.

Please see => https://medium.com/consensys-diligence/stop-using-soliditys-transfer-now-b1b6d2d00faf

I advice for to remove this error message, which is misleading for the developers.

@avatar-lavventura avatar-lavventura changed the title Consider using 'transfer' in place of 'call.value() is wrong for solc > v0.6.0 “Consider using 'transfer' in place of 'call.value()” is a false error message Mar 7, 2020
@avatar-lavventura
Copy link
Author

avatar-lavventura commented Jan 18, 2022

"Consider using transfer in place of 'call.value()`" is a false error message by ethlint (https://ethereum.stackexchange.com/q/80402/4575)

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

No branches or pull requests

1 participant