- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 May 2019 15:10:18 +0000
- To: public-houdini-archive@w3.org
For type parsing, whatever future solution is chosen, I hope it has a way to apply to variables as well as to functions. But for our Level 1 Custom Functions, if type checking isn't handled until the function returns a (TypedOM) value, then we don't need a declared `returnType` on the class or configuration option object. Which gets rid of another issue I'd thought of — how to represent functions where the return type is dependent on the input parameter types? ________________ I'm adding this to the next Houdini F2F agenda, to get consensus from the larger group on the idea & the Level 1 limitations to it. I think the main question still to debate is whether to base the API around a class object or around a configuration dictionary. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/857#issuecomment-488309530 using your GitHub account
Received on Wednesday, 1 May 2019 15:10:19 UTC