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

Reflection types #33

Open
Naddiseo opened this issue Jun 12, 2015 · 5 comments
Open

Reflection types #33

Naddiseo opened this issue Jun 12, 2015 · 5 comments

Comments

@Naddiseo
Copy link
Collaborator

Do we need to do anything regarding this: https://github.com/alex-weej/es-reflect-type-proposal

@lukescott
Copy link
Owner

If there is any reflection in JavaScript, there needs to be a way to get the type of each argument and the result type of a function (most likely). So I would say: Yes we need to do something regarding reflection, depending on how that takes shape.

@Naddiseo
Copy link
Collaborator Author

Okay, all the problems I'm thinking up now are due to this issue. I think we should not do reflection in this proposal, and let the es-reflect proposal handle turning hints into reflectable types (assuming hints are put into the language first), or have a second proposal afterwords "es-hint-reflection" to deal with hints+reflection.

@lukescott
Copy link
Owner

I'm not sure we can completely ignore reflection. Considering it's part of another proposal, perhaps we can do a separate .md file that describes how it would work with reflection. We should do something similar with #31 (Typed Objects).

@lukescott
Copy link
Owner

Hmm... is that even in stage 0? I don't see it here: https://github.com/tc39/ecma262/blob/master/stage0.md

@Naddiseo
Copy link
Collaborator Author

It is a strawman at the moment, posted on the es-discuss mailing list. So, yeah, lets ignore reflection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants