Michael

Considering the following example, how many iterations do we expect? Currently, we determine the loop-terminating predicate depending on whether or not the `STEP` variable is positive or negative upon entering...

…so they can be used in initializers. Adds a new `{constant}` pragma for POUs, however for now only the builtins are actually allowed to make use of it. This enables...

Adds a new variable block type for `VAR_EXTERNAL` to the compiler. These blocks do not have any functionality for now and the compiler will emit a warning when such blocks...

Adds a new global validation to check if all template variable instances have a matching configuration. Additionally validates if a template variable is configured more than once.

**Describe the bug** The following example will hit an unwrap in https://github.com/PLC-lang/rusty/blob/bca3c3179ea8752093e3b8654226fbc646b69a6f/src/validation/variable.rs#L246-L251 when the declared type does not exist. **To Reproduce** try to compile with `--check`: ``` VAR_GLOBAL y: BOOL;...

With #1301 we submitted a fix to prevent the pre-processor to generate multiple global variables mapping the same address variable, e.g.: ``` VAR_GLOBAL foo AT %IX1.2.3.4 : BOOL; bar AT...

When trying to formally assign an input-parameter with the removed address-of operator `&`, `--check` will not report any errors. ``` VAR_GLOBAL global : DINT; END_VAR PROGRAM prog VAR_INPUT input :...

In the current implementation of the initializer functions, data types are unconditionally initialized with their declared type-initializer. If a new initializer is set for an instance, it is currently not...

Currently, reference initializers are only supported for global target variables (and stack-local members, i.e. functions and `VAR_TEMP`). It would be nice to extend the alias functionality to work with local...

Now that we are generating quite a bit of code internally in the compiler, we should make sure none of this generated code also generates debug infos, since this could...