Super interesting that Rust/C++/Swift have all converged on similar ideas for collections & identity but with different cost profiles.
The Swift strategy seems to be to make safety checks dynamic when it makes coding more convenient, then optimize the checks away.
-
-
yes, it's made by the llvm devs, after all. A fun optimization challenge!
-
(there are places where this isn't strictly true -- non-escaping closures are the default)
-
implicitly unwrapped optionals are also being de-emphasized, afaict
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.