Zilin Chen
Zilin Chen
Many of the missing things are on my wip-reftypes branch. Since on master there's no typechecking for array operations, many things were left out as they weren't needed or didn't...
The easy solution is to reject `after` layouts if its offset depends on layout variables. The ultimate solution is to add `after` to Core.
A semi-related things is, having quasiquotation we can probably get rid of the .ac files.
Rust's macros look more intuitive than TemplateHaskell for systems users.
thinking about it more, handling indentations in macros could be challenging; in particular we don't always have the more explicit form with delimiters.
Am I missing anything? You need to write concrete syntax in the macro definitions. E.g. ``` macro_def X ($pat:p) = [| | Success p -> 0 |] foo : ->...
But still, ``` macro_def X ($exp:a) = [| a | Success p -> 0 | Error _ -> 1 |] ``` How do you align the two guards? We'll have...
Hmmm. Don't know if it's powerful enough if we want to use them to generate ad hoc polymorphic functions, generate glue functions to convert between C and Cogent data structures,...
Also, right now Dargent doesn't generate getters and setters which are not used in Cogent.
8d7e015 fixes the first problem, and also parens around the RHS of `:~` is no longer required.