[swift-evolution] [Review] SE-0138 UnsafeBytes

Karl razielim at gmail.com
Fri Sep 2 21:36:55 CDT 2016

>  * What is your evaluation of the proposal?


>  * Is the problem being addressed significant enough to warrant a
>    change to Swift?


>  * Does this proposal fit well with the feel and direction of Swift?

Yes, but I’m not sure about the “Unsafe” part of “UnsafeBytes” — what is unsafe about getting the byte-representation of a value?

As I understand it, “Raw” is what we use for “untyped”, so might I suggest “RawBytes"?

>  * If you have used other languages or libraries with a similar
>    feature, how do you feel that this proposal compares to those?

Don’t know; maybe, I can’t remember. Better than what we would otherwise have for Swift 3, in any case.

>  * How much effort did you put into your review? A glance, a quick
>    reading, or an in-depth study?

Read the proposal, glossed over the previous discussion. I’ve had similar trouble deciphering the new API, so I sympathise with the demonstrations.

> More information about the Swift evolution process is available at
>  <https://github.com/apple/swift-evolution/blob/master/process.md>
> Thank you,
> -Dave Abrahams
> Review Manager
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list