4 ms·
But, if you're assuming EsDoc, you're already inherently tied to JavaScript/TypeScript/etc, no? Part of the point of the paper is assuming non-uniformity betwe
by cmeiklejohn 9y ago
But, if you're assuming EsDoc, you're already inherently tied to JavaScript/TypeScript/etc, no?
Part of the point of the paper is assuming non-uniformity between APIs, hence the IDL.
- cmeiklejohn 9y agoAlso, it remains unclear how you expect to support parametric polymorphism if you're assuming JavaScript as a base language for your analysis.
- keithwhor 9y agoWhat can I say? We’re a team of hackers. It’s not our goal to solve every problem immediately, just the ones facing us and our developers today. We wanted an abstraction simple enough to ship to our community and customers but robust enough, conceptually, to be built out into a fully expressive language. (Hence FaaSlang.) ESDoc is JavaScript specific, but the concept of relying on comments to infer types is not, nor is the JSON format we store function execution information in. :) (Well, I mean, we rely on JavaScript-translatable types — but can create parallels to other runtimes and languages.)