qi
qi copied to clipboard
drym-org
An embeddable flow-oriented language.
How can we identify list-like operations done on values? See [A Core Performance Issue Identified](https://github.com/drym-org/qi/wiki/Qi-Compiler-Sync-Jan-6-2023). This would allow us to leverage the existing deforestation pipeline for pure values transformations. We...
E.g. wrt. termination of passes. Define a reference compiler and optimizing compiler. Elaborate the sequence of compilation for an input expression in the reference compiler vs the optimizing compiler. Related:...
E.g. selective binding `(as _ v _)`, packing values `(as u v . ws)`, and binding exceptions in `try` (#29 ). Also review the interaction of bindings with `clos`.
We've talked about [Qi Normal Form](https://github.com/drym-org/qi/wiki/Qi-Compiler-Sync-Aug-18-2023#qi-normal-form) a lot and have implemented a lot of normalization rules in the compiler, bu we haven't actually defined what Qi Normal Form is aside...
I guess capturing continuations in flo is an interesting idea. Assuming Qi supports `let/cc` form: ```racket (define-qi-syntax-rule (let/cc flo) (esc (λ args (let/cc cc (apply (☯ flo) cc args))))) (define-qi-syntax-rule...
@dzoep made a survey of `racket/list` and identified these APIs as candidates for deforestation (after the initial compiler release merging #74 ). **Consumers**: - [ ] cadr, caddr, cadddr, caddddr,...
Qi in many cases does not distinguish variadic functions from fixed-arity functions. We may be able to infer the appropriate arity in practice, and apply these functions to a specific...
We use `emit-local-step` to report compiler transformations as expansion steps, but this API doesn't capture the (tree-structured) context of expansion as normal Racket expansion does. Try unpublished expansion event APIs...
The [modular compiler architecture](https://github.com/drym-org/qi/pull/151) is a useful first step to making the compiler extensible (and for instance, is planned for use in [deforesting `racket/list` APIs](https://github.com/drym-org/qi/issues/118)), but it is only usable...
It appears that the Coverage step in the CI workflow fails when run on a pull request on any fork other than `drym-org` , with the following error: ``` curl:...