Zilin Chen
Zilin Chen
In a nutshell, defaulting implicit offset to `after` is not compatible with layout polymorphism. One concrete example is: ``` type PairBool = { a : Bool, b : Bool }...
``` type A = U32 three : A three = 3 foo : A#[three] -> A foo x = x@2 ``` It doesn't normalise `A` to `U32` before it converts...
Currently under development as a thesis project. Currently planed: * map C code locations back to Cogent (and antiquoted C) source code * map identifiers in the generated C code...
Current Status --------------------------------------- Most features are on master branch. Related Tickets --------------------------------------- #316 #290 #291 #246 #311 #310 #305 #278 Record field ordering: #313
We don't allow layouts to be under-specified for now. E.g., a Bool type can't be larger than 1 bit. This design simplifies C code generation a lot, and also makes...
In the current implementation, `V t1 t2` is equivalent to `V (t1, t2)`, even in the surface language. Shown by `misc/pass_differing-num-con-args-1.cogent` and `misc/pass_differing-num-con-args.cogent`. We may want to change this behaviour.
Synopsis ----------------------------------- It's an undergrad thesis project. The goal is to add recursive datatypes (e.g. Lists, Trees) into Cogent. It will be implemented in Minigent, and is being ported to...
Description --------------------------- Currently in the Cogent testsuite (https://github.com/NICTA/cogent/tree/master/cogent/tests), we only have two categories of test files, named `pass_*` and `fail_*`, which are tests which should pass or fail respectively. However...
Description ------------------------------------ The high-level idea is that, LLVM IR gives us more control (over performance) than relying on the optimiser of C compilers. A novel way to establish the Cogent-LLVM...
It'd be good to have a way in the new testing framework to turn on/off certain tests depending on the flags used in building the compiler.