[swift-evolution] Synthesizing Equatable, Hashable, and Comparable for tuple types

Tino Heth 2th at gmx.de
Mon Nov 27 02:44:25 CST 2017

> Why do you need to have this ability to unsafe bitcast? Is interconversion between point types such a common operation that it's a performance bottleneck?
A real-world example: Real-time image processing.
When you have a stream of 4k pictures at 30 fps, you really don’t wont to copy buffers just because two filters insist on having their own representation of bitmap data.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20171127/dfdd3f92/attachment.html>

More information about the swift-evolution mailing list