Baggers

See here https://github.com/cbaggers/varjo/blob/master/src/docs.lisp#L303 for the problematic docstrings

The following code `foo` is defined but the existing func from global is still used (returning a `foo-g` object) ``` (add-external-function 'foo '() '() '(1)) (defun test2 () (glsl-code (translate...

No type ref so it's stripped, however it causes an error. ``` Error compiling fragment-shader: 0(17) : error C0000: syntax error, unexpected '[', expecting "::" at token "[" // fragment-stage...

Less ugly hacks in the compiler and easier to reason about

Minimize side effects in base-env (taking flow analysis into account)

1

## possible current issues caused by this - Passing first class function [A} to function [B} inside loop can result in multiple copies of the function [A}

GLSL is call & return by value. Tweak the flow analyzer to acknowledge this

2

> 6.1.1 Function Calling Conventions > Functions are called by value-return. This means input arguments are copied into the function at > call time, and output arguments are copied back...

Move context fields to the environment

1

The way we handle this currently is very naive, it worked for the initial prototype but is painful to work with now. We need to parse each of the valid...

This is something that just worries me right now. I have had to make the check looser than I would like and I dont yet get the implications of the...

Review all public symbols and make sure they follow patterns. Some have `v-` at the front, some dont, some say 'args' some say 'variables' (are they either of those? or...

Along with these two issues https://github.com/cbaggers/varjo/issues/172, https://github.com/cbaggers/varjo/issues/43, we also need to be validating which qualifiers are valid in what places (in-args, uniforms, etc) We also need to incorporate the implications...