Re: [heycam/webidl] Allow constructor<ClassType> as a type accepted by functions. (#101)

I think we need to do something here. The current CustomElement and houdini specs are way too JS-y, error prone to maintain and implement.
(1) Looks like current specs using ctors and classes end up taking references to (all? some?) functions when class is passed as a callback. That is at least something which could be done in webidl layer, if it is something we actually want to do.
(2) Other option is to not explicitly store those functions and only just try to use them.

In both cases webidl layer would define what kind of class is expected. (and C++ side of bindings would see that kind of class and could call its methods. If option (2) was used, method call might fail because of the function not being there)

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/101#issuecomment-229825089

Received on Friday, 1 July 2016 00:29:35 UTC