Michael
Michael
**Is your feature request related to a problem? Please describe.** Currently, initializing an array with an unresolved reference will be caught during the codegen phase: ``` VAR x : ARRAY[0..UNRESOLVED_REF]...
**Is your feature request related to a problem? Please describe.** Some of the compile-time validations we have in place (e.g. implicit downcasts #828) produce a lot of false positives due...
**Is your feature request related to a problem? Please describe.** Currently, the following code compiles without warning/error: ```smalltalk FUNCTION foo: DINT foo := 1 / 0; END_FUNCTION ``` **Describe the...
**Is your feature request related to a problem? Please describe.** When trying to compile code with a comparison statement which tries to compare incompatible types, we currently do not validate...
**Is your feature request related to a problem? Please describe.** Currently we are not validating the amount of passed parameters to function calls. Calls with too many/too few parameters will...
**Is your feature request related to a problem? Please describe.** When trying to compile code with a binary statement which involves math operators with incompatible types, we currently do not...
It would be nice to extend our metrics dashboard to include data about the resulting binary sizes across changes. This could also be extended to track the build time/binary size...
Currently there is no validation in place for variables being initialized in variable blocks. Trying to initialize a variable with an invalid type will fail during codegen, but not be...
blocked by #1259 This PR adds generated init functions for each stateful POU and struct type regardless of whether or not the const_evaluator flagged it, resulting in changes to around...
This is the first in a series of PRs to enable support for complex initializers (e.g. initializing pointers with hardware addresses/addresses not known before allocation). This is achieved by lowering...