thank you for pointing this out!

Yes this would be kind of workaround based solution, but since it really looks like that the behaviour changed with the last swift version, I would like to address the problem.