Add documentation for inheritance #291
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This adds documentation for prototypal inheritance and gives a basic example, class based example, and functional example.
| @mpaarating It was great working with you. Looking forward to working with you :-) Star to the repo is highly appreciated. |
| @mpaarating The work you have done for the project is highly appreciated. Thanks :-) Looking forward to working with you on my new project related to Deno https://github.com/Swap76/Learn-Deno/ and together making this better. Star to the repo is highly appreciated. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Description
Per #189, this adds documentation for prototypal inheritance and gives a basic
example, class based example, and functional example. I assume there will be some shared discussion with the
Classesdocumentation, but felt that inheritance couldn't properly be discussed without mention the relationship of the class model and what happens under the hood.