[swift-evolution] What're the Swift team's thoughts on Go's concurrency?

Dmitri Gribenko gribozavr at gmail.com
Wed Aug 10 18:06:03 CDT 2016

On Wed, Aug 10, 2016 at 3:50 PM, David Sweeris via swift-evolution
<swift-evolution at swift.org> wrote:
> For example, maybe you really do need to interpret a 64-bit chunk of data as an Int64, even though the compiler is convinced it’s a Double. We can do that in Swift through the various “unsafe” functions, which is where they belong because 99.99% of the time that’s a bad idea.

"42.0.bitPattern".  Why do you think this conversion is unsafe?


(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

More information about the swift-evolution mailing list