The code is not valid, because it trips an assertion. I believe this pattern can miscompile in some cases, and there’s a bug that needs to be fixed.
Can we get consistent assertion behavior in the latest release Swift compiler across host platforms?
2 Likes