Hervé Yviquel

Does it mean the bug is solved ?

That's true, when do you plan to do it ?

Nop, we do not use the inliner anymore :wink:

@alorence The simulation is run once.. If it has failed because of an array out of bound exception, then an error is displayed at the given line into the editor....

btw, it is not possible to use the mechanism with the backends, since the applications are executed out of eclipse.

I know this issue: It is still unfinished work on the front-end/IR... According to the current semantic of the applications, we consider that arguments of type scalars are given by...

That maybe "5" should not be an uint of size 3: The size could be related to its use. Anyway, i don't like your explicit casting :-1:

`int t := ~( (int(size=4) 5);` is ugly, not in the standard, not really useful, etc. But, it is only my personal opinion :wink: . However, we have to add...

I'm agree with bool/int conversion... But, resizing an integer can always be done using a specific statement: It is not so painful to do...

After all, even bool/int conversion is not really useful: `(i = 1)` seems quite simple to convert them.