This bug is just as easy to express in Swift.

To eliminate this class of bug you need to eliminate statements, such as in Haskell.

you'll have to explain for that to mean anything. The associated web page doesn't give any information. Also what do you mean by removing statements.

Not sure how an Out-of-Bounds write (used in this exploit) could happen in Swift.

it uses the `NetworkExtension` framework to intercept all your communications and potentially modify them.

https://developer.apple.com/documentation/networkextension