Lukas Armborst

FWIW, I think that there are indeed multiple main classes, as we include other git repositories as dependencies, which have their own main method. The build.sbt even mentions multiple mains,...

FWIW, last week I already tried replacing the `wildcard` with fixed fractions, as well as adding some manual (naive) triggers. Neither seemed to fix the problem. A first look by...

Another option is to have `_Bool` be a `TCInt` rather than a `TBool`. Given that PR #1170 allows coercion from int to boolean, this should not cause too many problems,...

> this should not cause too many problems, right? So I tried it, and the CI fails in a few cases, e.g. https://github.com/utwente-fmt/vercors/actions/runs/8803794962/job/24163164935. It seems that coercing the boolean expression...

A SYCL test (https://github.com/utwente-fmt/vercors/blob/9ad14fc3ba0c637eb79275df16d279044fcee850/examples/concepts/sycl/buffers/WrongGenericArgumentForConstructorHostdataType.cpp) fails in the CI. It is a negative test that tries to instantiate an int buffer with a bool array, which should fail. It still does,...

Note: This also occurs with other parsing errors in C, such as _"This construct [...] is syntactically valid, but not supported by VerCors."_ Example (with `ParameterDeclaration1Context` not supported): ```c void...

Quick check in: I've tried a few things, but not all. - [ ] I have not tried modifying the code of VerCors to invoke `SetConsoleOutputCP`. - [x] running `chcp...

Note: It's not just predicates that cause this error in C, but also calling a regular method with the wrong parameter list.

Result of discussion today: - ghost fields are part of the class, and thus not an issue - so the question is mostly how to handle top-level specifications like in...

It seems to be a trigger issue: When putting the trigger braces only around `arr[i]`, without the `pairs`, then it stops complaining (it then complains about injectivity on the last...