Pekka Klärck

Ok. I would recommend you to implement the logic in Python so that you can directly use it from the variable file. You could then also expose the logic as...

I agree the return code should always be non-zero if execution ends for an error. Unfortunately handling `--exit-on-error` is somewhat tricky and this may not be that easy to implement....

@Snooz82 is right that this occurs because the keyword accepts `**named` and thus Robot considers all arguments using `=` to be named arguments. The proposal by @Snooz82 to ignore `=`...

It seems we forgot about the idea to use positional-only arguments for this usage. I believe it would be pretty useful and we could try doing that in RF 7.1....

This is a known problem and reported already in #4293 and #4422. We have decided to not change the default teardown behavior, but instead made it possible to explicitly change...

I agree we should investigate how hard changing the behavior would be and what kind of effect it would have. It will be at least somewhat backwards incompatible change, so...

This is fine if it's possible to specify only the package, but if you needed to specify all types separately like ```python class Example(SuiteVisitor[TestSuite, TestCase, Keyword, If, IfBranch, Try, TryBranch,...

Do you have ideas how to implement this without making the visitor implementation horribly complicated? Mypy compatibility isn't a goal for us for various reasons, one of them Mypy being...

Having separate visitors for the running and result model would certainly be easier for users than needing to list all possible item types with `SuiteVisitor[...]`. That said, I don't consider...

It's not enough for to make just `TestSuite` and `TestCase` generic, that needs to be done with `Keyword`, `If`, etc. as well. A problem is that if/when we add more...