mariari

### Updated plan After much thinking about the solution, I've thought of a plan. We utilize the fact that common lisp functions can be `compiler-macros` as well. Thus we wrap...

## Updated Plans Again After a prototype on #33 where I implemeneted an automatic stack pusher ```lisp (defmacro stack-compiler-macro (name) `(define-compiler-macro ,name (&whole form &rest args) "Adds pushing stack traces...

Work has been mostly completed, code by default is traced, all that is left is making the traces readable and noting where function boundaries are for the work I need.

Further the new work from `VAMP-IR` shows that they now support records, meaning that a bulk of the work can be simplified for this use case. Current Issues caused by...

This has further issues, as even code like ```lisp (defcircuit array-from-data-check-consts ((output (array int 10))) (def ((bar (to-array 36))) (prld:+ (prld:check 5 (int 32)) (prld:get bar 0)))) ``` causes issues,...

This has been done for the `vamp-ir` IR inside of alucard. However this is needed for the top level data structure

Edit: With the following change ```lisp @@ -216,7 +216,8 @@ of the user program is preserved." (list (ir:var term)))) (ir:make-multiple-bind :var nil :val (ir:value term))) ((and (typep value 'ir:reference) -...

I manage to get a small reproducible case that might be related to this ```elixir @spec indirection(number(), number(), non_neg_integer()) :: list({atom(), list(), binary()}) def indirection(storage, key, order) do [:hi, [],...