Ok I see your point about the stack. However your solution would need a lot of changes I the programs and additionally we would need to document the rule to implicitly avoid stats calculation by adding_work to the end of the program. So I was thinking why not introduce a way to explicitly state that no stats update is required / foreseen for a work program. This could probably be done by defining a new return state. Alternatively I'm asking myself if we should not try to return=None or return= to avoid stats calculation without having a skipped state. -- https://code.launchpad.net/~widelands-dev/widelands/bug-1786613-10s-return-skipped/+merge/353449 Your team Widelands Developers is subscribed to branch lp:~widelands-dev/widelands/mines-worldsavior.
_______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : widelands-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
