-
Notifications
You must be signed in to change notification settings - Fork 212
Add a feature specification for the metaobject proposal #4301
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
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
Lots of improvements, PTAL!
The change to a more abstract approach does get a little bit silly when we have to reinvent covariant
along the way, but it does also make some other things simpler. I think it's a slight improvement on average.
However, it's a major point in the design of this feature that it does not introduce a lot of completely new from-scratch primitive semantics, it is simply a way to transform a type C<T1 .. Tk>
to an object MetaC<T1 .. Tk>
, and all the expressive power follows from that, based on well-established mechanisms like superinterfaces, overriding declarations, etcetc.
a2bab3b
to
3db7641
Compare
This PR adds a feature specification for the metaobject proposal (formerly known as 'more capable Type objects'). For simplicity, it does not include the part about
Type.reify
(that will be specified separately).