-
Notifications
You must be signed in to change notification settings - Fork 291
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
[WIP] Begin documenting HOW archetypes and document parameterization #3160
Conversation
Passes xtest, thanks. |
Is this still a draft? Can it be used? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few comments, since this is still a work in progress.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In principle: this would be a useful addition.
Sorry for the processing delay: can you fix the branch conflicts? |
Hand applying a patch submitted by Kaiepi in #3160 from 2020. Much thanks.
Hand applied in 399ec64. |
The problem
See #3132
Solution provided
Parametricity is an archetype; archetypes are currently undocumented. This begins the process of documenting them, documents how parameterization works, and provides some examples of how parametric classes can be used.
I'm having some trouble coming up with a practical example of using mixins with the
parameterize
metamethod. MyKind
ecosystem module does this, but it doesn't make a very good example because of the reasoning behind its use.