Split typing from rest of type checker

[turbolent]

Issue to be solved

Currently, the checker is implemented in a way where determining the type of an expression and other checks, like if an expression can be assigned to (which has e.g. the side-effect of reporting an error), is interleaved.

In certain cases it is necessary to determine the type of an expression without any checks, as the result is needed as an input for checking another expression.

Suggested Solution

Split typing, determining the type of an expression, from the rest of the expression checking.

[SupunS]

Now that we are done with major changes to the type-checker, and don't have any on-going work either, probably a good time to get started on this. I can have look and maybe draft something together, and then we can evaluate. Or do you have any specific ideas in mind?

[j1010001]

Affecting our ability to address security reports