Michael

**Is your feature request related to a problem? Please describe.** While - as far as I can tell from the grammar in the standard - this functionality is not required,...

Add `--release` tests to our CI

1

We should add release testing to our CI to get ahead of future issues regarding release builds.

Misleading error message when calling `MUX` with aggregate types of different sizes and/or types

1

When compiling the following example, the error messages printed to console are quite interesting. ``` FUNCTION main : DINT VAR arr : ARRAY[0..3] OF DINT; okay : ARRAY[0..3] OF DINT;...

Currently our parser errors could do with some improvement. Take the follwing example, where I am trying to declare a variable with a reserved keyword as name: ``` FUNCTION main...

`MUL_LTIME` returns different values depending on if the stdlib is built with `debug` or `release`

1

**Describe the bug** Given the following example: ``` {external} FUNCTION printf : DINT VAR_INPUT {ref} format : STRING; END_VAR VAR_INPUT args : ...; END_VAR END_FUNCTION FUNCTION main : DINT VAR...

**Describe the bug** While testing edge cases for #1165 i came across an unsual assignment diagnostic. Trying to get the address of a qualified action reference `ADR(FOO.BAR)` validates an assignment...

Unary expression `+ <REAL>` panics on `unimplemented!()`

1

**Describe the bug** Unary expressions with an explicit `+` operator on REALs will panic in https://github.com/PLC-lang/rusty/blob/b357a05cb064eb21fed110b6d7c5f543f72c18e8/src/codegen/generators/expression_generator.rs#L400 The same expression with INTs is fine. **To Reproduce** This came up while porting...

Sort error codes within their categories when printing with `plc config diagnostics`

1

**Is your feature request related to a problem? Please describe.** Currently, if you want to see the error severity configuration and print it via `plc config diagnostics`, the error codes...

Parsing cast expressions assumes expression to be atomic leaf expression

3

**Describe the bug** Currently, parsing something like `INT#(a + b)` or `INT#UINT#16#FFFF` is not possible, since our parser will always call `parse_atomic_leaf_expression` right after matching a `TypeCastPrefix` token. A possible...

**Is your feature request related to a problem? Please describe.** ``` FUNCTION main : DINT VAR a : INT := 65535; // warning b : INT := 16#FFFF; // warning...