-
Notifications
You must be signed in to change notification settings - Fork 398
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
Docs Request: Payable, and an explicit comparison of transfer(), send(), and call() #260
Comments
@briandoyle81CB , I would like to contribute to this, i have added an article for Payable. Let me know if something needs to be changed. I will add an article for comparison of transfer(), send(), and call() also. |
@hoysal08, do you still intend to write the second article? No worries if not, I just don't want to open it up to others if you're working on it. |
Hey @hoysal08! Happy to pick up this article or collaborate on it if you are working on other things... Will give it a few days to hear back and start after ETHDenver wraps up if I don't hear back! If you are going to continue you with it then I look forward to reading! |
@hoysal08 checking back in as I'm back from ETHDenver. Will start this evening if I don't hear back! Let me know if you want to collab |
Hey @twynne20 , sorry for the delay. I was held up with something else. |
Thanks for the response @hoysal08. Perhaps I will do some PRs once yours is merged if I see any value I can add. I wrote up an initial article as well. If you are still adding to your PR here is the current article I wrote if you want to check it out in Notion. (Didn't PR yet) Feel free to pull any info you like from it: |
What is the issue you are encountering with the docs?
Add a section on payable, and an explicit comparison of transfer(), send(), and call()?
Links to Impacted Docs
n/a
Describe the solution you'd like to see.
Payable, and an explicit comparison of transfer(), send(), and call()
Additional context
No response
The text was updated successfully, but these errors were encountered: