mariari
mariari
With the last commit, explciit voids can be generated from standalone `with-constraint`. This means that the code currently generates out a void with the following code ```lisp (defcircuit range-check ((private...
Currently the `setf` interface for array setting is quite imperative. which makes it clash with the compilation model, however @paulcadman suggested a more functional form like ```lisp (defcircuit array-creation-check ((output...
with #22 we have operations to introduce type variables to the typing context. We should use this for the rest of compilation to better compile addition mod some number.
With the advent of #22 I've left some holes, namely: ```lisp ;; src;typechecker;typecheck.lisp (-> annotate-term-no-binder (ir:term-type-manipulation typing-context) (values typing-result typing-context)) (defun annotate-term-no-binder (term context) "Annotating a term can either end...
Would be nice to use a standard pipeline object that I can pass around information along with a body
Alucard as a language is quite limited, further the type system is also quite limited. Due to this I'd like to introduce the folloiwng primitives 1. `(type-of foo int)` -...
### Preamble Currently I don't store any source information when I do my compiler transformations. What this means is that error messages are going to be quite ugly. Further it...
Currently I ignore public private parameters. However with little work we can get public parameters to functions to emit when we dump the entry point to the circuit. Care has...
We should have light weight syntax for defining circuits along with privacy and type information. Currently we do everything in `defcircuit` but most functions are not the entry point and...
Leo has a good section on how to test [given circuits](https://developer.aleo.org/developer/language/tests). We too can give out good documentation on how to test circuits. With #6 we can just run circuits...