I don't think this is the correct call here.
Just that a constructor has no argument does not mean it is a propagated default constructor.

Fixes an issue where Std::List would implement Iterable and therefore break the scripts.

fixes issue about unknown type parameters for StdLibs::List

This reverts commit 95d9aa2b32.

Now instead uses Objects.toString(...) for them

Reason was that it tried to invokeInterface whereas a bridge redirects to a local (virtual) method.
The local method was flagged incorrectly as the same type as the bridger which would be interface, hence the error

Essentially they are functions that accept the parsedExpression and the compilescope.
They return either null or a PartialExpression.
If they dont return null then the used partialexpression will be used instead of whatever the parsedexpression wouldve compiled to

Now pritns the array element type and the faulty element's type
Also changed this for assoc Arrays

Only WIP, tries to check the same type without storage tags and see if it can cast then.

They worked in my simple, void test example

The Optional annotation is parameter, not type bound

WIP: Not really tested and contains RuntimeExceptions that I used for testing
WIP: Not all possible return types covered
WIP: Not really clear which order/priority some statement contents should be checked
WIP: Not dealing with type mismatches or one branch returning something a subclass of the other branch's return type

E.g. IIngredient has a method that accepts an IItemStack, which is a sub-interface