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

self is not properly documented #1716

Closed
iamdefinitelyahuman opened this issue Nov 11, 2019 · 0 comments · Fixed by #1787
Closed

self is not properly documented #1716

iamdefinitelyahuman opened this issue Nov 11, 2019 · 0 comments · Fixed by #1787
Labels
documentation Documentation Easy Pickings Used to denote issues that should be easy to implement

Comments

@iamdefinitelyahuman
Copy link
Contributor

The only references to self in the documentation are in the examples, and briefly when explaining how to call a private function. Given this is a fairly fundamental variable when writing Vyper contracts, it deserves some proper documentation.

Related, re: #1696, we should very clearly document that Vyper disallows external calls back into the same contract, the rationale behind this, and (once the issue is closed), how to perform this action via raw_call.

@jacqueswww jacqueswww added documentation Documentation Easy Pickings Used to denote issues that should be easy to implement labels Nov 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation Easy Pickings Used to denote issues that should be easy to implement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants