Why will RawByte be deprecated in Swift 3?

marco.masser · 2016-02-12T10:34:18.000Z

There’s a RawByte struct in the Swift 2.2 standard library:

/// A byte-sized thing that isn't designed to interoperate with
/// any other types; it makes a decent parameter to
/// `UnsafeMutablePointer<Memory>` when you just want to do bytewise
/// pointer arithmetic.
@available(*, deprecated, message="it will be removed in Swift 3")
public struct RawByte {
}

Why is that deprecated? On the current Swift master branch (22c4d7d) it’s still used in the String-related code and there’s also no mention about it being deprecated. Is there a replacement for RawByte? Should I just write my own version when I don’t want Int8 or UInt8 to mean “just a byte”?

Bonus question: Where does this deprecation come from? How can something be deprecated in the public Swift release when it’s not deprecated in the Swift source?

Cheers,

Marco

gribozavr · 2016-02-13T04:38:26.000Z

There’s a RawByte struct in the Swift 2.2 standard library:

/// A byte-sized thing that isn't designed to interoperate with
/// any other types; it makes a decent parameter to
/// `UnsafeMutablePointer<Memory>` when you just want to do bytewise
/// pointer arithmetic.
@available(*, deprecated, message="it will be removed in Swift 3")
public struct RawByte {
}

Why is that deprecated? On the current Swift master branch (22c4d7d) it’s
still used in the String-related code and there’s also no mention about it
being deprecated. Is there a replacement for RawByte? Should I just write my
own version when I don’t want Int8 or UInt8 to mean “just a byte”?

Using UInt8 or Int8 is recommended.

Bonus question: Where does this deprecation come from? How can something be
deprecated in the public Swift release when it’s not deprecated in the Swift
source?

It comes from a preview implementation of SE-0006

github.com

apple/swift-evolution/blob/main/proposals/0006-apply-api-guidelines-to-the-standard-library.md

# Apply API Guidelines to the Standard Library

* Proposal: [SE-0006](0006-apply-api-guidelines-to-the-standard-library.md)
* Authors: [Dave Abrahams](https://github.com/dabrahams), [Dmitri Gribenko](https://github.com/gribozavr), [Maxim Moiseev](https://github.com/moiseev)
* Review Manager: [Doug Gregor](https://github.com/DougGregor)
* Status: **Implemented (Swift 3)**
* Decision Notes: [Rationale](https://forums.swift.org/t/accepted-with-modifications-se-0006-apply-api-guidelines-to-the-standard-library/1667)

## Reviewer notes

This review is part of a group of three related reviews, running
concurrently:

* [SE-0023 API Design Guidelines](0023-api-guidelines.md)
  ([Review](https://forums.swift.org/t/review-se-0023-api-design-guidelines/1162))
* [SE-0006 Apply API Guidelines to the Standard Library](0006-apply-api-guidelines-to-the-standard-library.md)
  ([Review](https://forums.swift.org/t/review-se-0006-apply-api-guidelines-to-the-standard-library/1163))
* [SE-0005 Better Translation of Objective-C APIs Into Swift](0005-objective-c-name-translation.md)
  ([Review](https://forums.swift.org/t/review-se-0005-better-translation-of-objective-c-apis-into-swift/1164))

This file has been truncated. show original

Dmitri

···

On Fri, Feb 12, 2016 at 2:34 AM, Marco Masser via swift-users <swift-users@swift.org> wrote:

--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr@gmail.com>*/

marco.masser · 2016-02-15T12:00:56.000Z

There’s a RawByte struct in the Swift 2.2 standard library:

/// A byte-sized thing that isn't designed to interoperate with
/// any other types; it makes a decent parameter to
/// `UnsafeMutablePointer<Memory>` when you just want to do bytewise
/// pointer arithmetic.
@available(*, deprecated, message="it will be removed in Swift 3")
public struct RawByte {
}

Why is that deprecated? On the current Swift master branch (22c4d7d) it’s
still used in the String-related code and there’s also no mention about it
being deprecated. Is there a replacement for RawByte? Should I just write my
own version when I don’t want Int8 or UInt8 to mean “just a byte”?

Using UInt8 or Int8 is recommended.

OK, I settled on typealias Byte = UInt8 within my Socket type, so it’s Socket.Byte now.

Bonus question: Where does this deprecation come from? How can something be
deprecated in the public Swift release when it’s not deprecated in the Swift
source?

It comes from a preview implementation of SE-0006
https://github.com/apple/swift-evolution/blob/master/proposals/0006-apply-api-guidelines-to-the-standard-library.md

Ah, missed that one in the diffs. Thanks for pointing it out.

Cheers,

Marco

···

On 2016-02-13, at 05:38, Dmitri Gribenko <gribozavr@gmail.com> wrote:
On Fri, Feb 12, 2016 at 2:34 AM, Marco Masser via swift-users > <swift-users@swift.org> wrote: