Is it now safe to error on unknown symbol?

[hexaredecimal]

I discovered a bug while coding compile-time warnings into the type-inference. Turns out when resolving pattern capture variables I would index the pattern type like an array instead of indexing the inner types. This led to weird errors (I would put a symbol with type undefined) that prevented me from getting the correct values. This caused the compiler to think certain symbols were undefined. Especially the usage of pattern vars inside the pattern body.

This fix should allow me to turn the compile-time warning into an error immediately

[hexaredecimal]

The only issue now blocking this bug fix is how recursive functions are handled by the typechecker. For now when a function is recursive it cannot see its definition on the env. This causes the compiler to print the warning