Rachit Nigam

Yeah! This is also important to get parity with the original flow which ran type checking before and after monomorphization (as a sanity check).

A relevant reading here is [liquid types](https://goto.ucsd.edu/~ucsdpl-blog/liquidtypes/2015/09/19/liquid-types/) which also allow for reasoning of predicates over types in a decidable manner. Maybe one way to decide which functions (like `pow2` and...

Is there anything actionable with this issue? If not, let's close it.

Elide bundle type binding if the parameter is unused: ``` bundle foo[N]: [G, G+1] 32 ``` In this case, all the indices in the bundle have the same availability.

For reference, here is an implementation of [Queues in Calyx](https://github.com/cucapra/calyx/blob/master/calyx-py/calyx/queue_call.py).

Fstar has a similar idea with the [`Lemma` return type](https://www.fstar-lang.org/tutorial/book/part1/part1_lemmas.html) that they use to describe [libraries of helpful axioms]( https://github.com/FStarLang/FStar/blob/master/ulib/FStar.Math.Lemmas.fst#L66).

In some ways, this is not a hard change to make. We need to make `Comp[Params]::Param` an expression so that it can be used anywhere. One consequence of this is...

Not sure if I've mentioned this before but the following command will print out the program AST after each pass in the existing compiler flow: ``` cargo run -- --log...

Oh awesome, this seems super useful. I guess the best way of representing complex numbers would come from something like #99 but this seems orthogonally useful. I think the first...

@UnsignedByte this is marked as "needs triage" but it seems the design is clear: write this as an abstraction in the AST/frontend and compile it away by the time we...