Jerome Simeon

This list isn't very useful without details on what those names are (variable names? type names? record field names?), and whether they are internal information to a phase (e.g., there...

@codetronaut Great that you're interested to help! I'm not really familiar with exiftool. My understanding of the suggested change was to support something along the lines of JSDoc for JavaScript:...

A few initial pointers: - Extracting metadata from Ergo functions (e.g., names, type signatures) will require getting familiar with the Ergo AST which is in Coq (https://github.com/accordproject/ergo/blob/master/mechanization/Ergo/Lang/Ergo.v) - If we...

Hi @codetronaut I think it would be good to have a description for what the feature should be from a user point of view first? Depending on that we can...

> Ok @jeromesimeon where should i put the "helloworld.ts"? That's a really good question. I would put it in e.g., `./tests/typescript` for now. We can see later if we find...

> I'm writing a little example with some functions but I think that for a real test should be used this package: https://github.com/SamVerschueren/tsd Hi @j4m3sb0mb it's been a while since...

Is there any plan to support this feature (based on @tmpfs 's work or other) in a future release?

> I made some progress in [9578251](https://github.com/querycert/qcert/commit/957825182862a98f44f9f398ff1e49c8ef8f7d33). > I think implementing and debugging the runtime would benefit from a set of unit tests per operator. How would you do it?...

> I'd implement them in imp_ejson. Makes them reusable for other backends / runtime implementations. agreed. Not sure how to make those systematic, would we like a syntax for those...

> Your imp_ejson parser undestands runtime operators like `Runtime.array(arg0, ...)`. How much effort is it to do something similar for non-runtime Operators? E.g. something like `Op.object(keys)(val1, val2)` which translates directly...