Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

We removed "of" from the final version: https://github.com/apple/swift-evolution/blob/master/proposals/0101-standardizing-sizeof-naming.md And moved it to "If for some reason, the core team

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jul 12, 2016, at 17:03, Dave Abrahams wrote: > > > on Tue Jul 12 2016, Jordan Rose > wrote: > >>> On Jun 30, 2016, at 12:30, Dave Abrahams via swift-evolution >>> wrote: >>> >>> >>> on Wed Jun 29 2016, Erica Sadun

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jul 12 2016, Jordan Rose wrote: >> On Jun 30, 2016, at 12:30, Dave Abrahams via swift-evolution >> wrote: >> >> >> on Wed Jun 29 2016, Erica Sadun wrote: >> > On Jun 29, 2016, at 3:59 PM, Xiaodi Wu via swift-evolution

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 12:30, Dave Abrahams via swift-evolution > wrote: > > > on Wed Jun 29 2016, Erica Sadun wrote: > >>> On Jun 29, 2016, at 3:59 PM, Xiaodi Wu via swift-evolution >>> wrote: >>> >>> On Wed, Jun 29, 2016 at 4:50 PM,

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jul 1, 2016, at 8:57 AM, John McCall via swift-evolution > wrote: >> On Jun 30, 2016, at 10:41 PM, Xiaodi Wu > > wrote: >> On Fri, Jul 1, 2016 at 12:03 AM, Dave Abrahams via swift-evolution >>

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 10:41 PM, Xiaodi Wu wrote: > On Fri, Jul 1, 2016 at 12:03 AM, Dave Abrahams via swift-evolution > > wrote: > > on Thu Jun 30 2016, John McCall wrote: > > >> On Jun 30, 2016, at 6:12 PM,

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jul 1, 2016, at 1:03 AM, Dave Abrahams via swift-evolution > wrote: > > It's not the minimum though. Just go with stride already  > Changing to stride. > Sent from my illudium Q-36 explosive space modulator -- Sent from the HQ of the Ravenous Bugblatter

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

On Jun 30, 2016, at 9:12 PM, Dave Abrahams via swift-evolution wrote: > I don't believe that “stride” *is* the accepted term of art for this > meaning. I never heard of the idea of types having an intrinsic > “stride” until I arrived on the Swift project. That usage

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Bah, of course. No point in trying to qualify the word; let's just call it the memory layout stride and be done with it. On Fri, Jul 1, 2016 at 02:05 Dave Abrahams wrote: > No, actually both can be something other than the minimum. These are > usually going to be the

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

No, actually both can be something other than the minimum. These are usually going to be the minimum-without-performance-degradation. Sent from my illudium Q-36 explosive space modulator > On Jun 30, 2016, at 11:29 PM, Xiaodi Wu wrote: > > I don't think it needs

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

It's not the minimum though. Just go with stride already  Sent from my illudium Q-36 explosive space modulator > On Jun 30, 2016, at 10:49 PM, Jacob Bandes-Storch wrote: > > There seems to be agreement that "stride" is sensical term for the distance > between values in

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

I don't think it needs qualifying. It cannot be anything other than the minimum, just like we have `alignment` instead of `minimumAlignment`. On Fri, Jul 1, 2016 at 00:50 Jacob Bandes-Storch via swift-evolution < swift-evolution@swift.org> wrote: > There seems to be agreement that "stride" is

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

There seems to be agreement that "stride" is sensical term for the distance between values in memory, but it seems like what MemoryLayout wants to expose is the *minimum* possible stride for a particular type. How do folks feel about "*minimumStride*"? On Thu, Jun 30, 2016 at 10:46 PM, James

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 10:07 PM, Dave Abrahams wrote: > > > on Thu Jun 30 2016, Matthew Johnson wrote: > >>> On Jun 30, 2016, at 8:12 PM, Dave Abrahams wrote: >>> >>> >>> on Thu Jun 30 2016, Matthew Johnson >> >

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Thu Jun 30 2016, Matthew Johnson wrote: >> On Jun 30, 2016, at 8:12 PM, Dave Abrahams wrote: >> >> >> on Thu Jun 30 2016, Matthew Johnson > > wrote: >> > >>> Sent from my iPad >>> On Jun 30, 2016, at 6:59 PM, Erica Sadun via

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 6:12 PM, Dave Abrahams via swift-evolution > wrote: > on Thu Jun 30 2016, Matthew Johnson > wrote: > >> Sent from my iPad >> >>> On Jun 30, 2016, at 6:59 PM, Erica Sadun via swift-evolution >>>

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

On Thu, Jun 30, 2016 at 8:21 PM, Matthew Johnson via swift-evolution < swift-evolution@swift.org> wrote: > > On Jun 30, 2016, at 8:12 PM, Dave Abrahams wrote: > > > on Thu Jun 30 2016, Matthew Johnson > wrote: > > Sent from my iPad > > On

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Thu Jun 30 2016, Matthew Johnson wrote: > Sent from my iPad > >> On Jun 30, 2016, at 6:59 PM, Erica Sadun via swift-evolution >> wrote: >> >> On Jun 30, 2016, at 5:47 PM, James Berry wrote: On Jun 30, 2016, at 4:05

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Sent from my iPad > On Jun 30, 2016, at 6:59 PM, Erica Sadun via swift-evolution > wrote: > > >>> On Jun 30, 2016, at 5:47 PM, James Berry wrote: >>> >>> >>> On Jun 30, 2016, at 4:05 PM, Dave Abrahams via swift-evolution >>>

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 4:59 PM, Erica Sadun wrote: > > >> On Jun 30, 2016, at 5:47 PM, James Berry > > wrote: >> >>> >>> On Jun 30, 2016, at 4:05 PM, Dave Abrahams via swift-evolution >>>

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 5:47 PM, James Berry wrote: > >> >> On Jun 30, 2016, at 4:05 PM, Dave Abrahams via swift-evolution >> wrote: >> on Thu Jun 30 2016, Erica Sadun wrote: >> On Jun 30, 2016, at 4:41 PM, Dave Abrahams

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 4:05 PM, Dave Abrahams via swift-evolution > wrote: > on Thu Jun 30 2016, Erica Sadun wrote: > >>> On Jun 30, 2016, at 4:41 PM, Dave Abrahams wrote: I mentioned this in a comment on the gist already, but I'm really

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 5:05 PM, Dave Abrahams wrote: > > > on Thu Jun 30 2016, Erica Sadun wrote: > >>> On Jun 30, 2016, at 4:41 PM, Dave Abrahams wrote: I mentioned this in a comment on the gist already, but I'm really not digging the

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Thu Jun 30 2016, Xiaodi Wu wrote: > On Thu, Jun 30, 2016 at 2:30 PM, Dave Abrahams wrote: > >> >> on Wed Jun 29 2016, Erica Sadun wrote: >> >> >> On Jun 29, 2016, at 3:59 PM, Xiaodi Wu via swift-evolution < >> swift-evolution@swift.org> wrote: >> >> >> >> On Wed, Jun

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 30, 2016, at 12:30 PM, Dave Abrahams via swift-evolution > wrote: > > I am still very skeptical that anyone needs the “Value” version, and as > long as we're resyntaxing I am inclined to take it away and see how many > people complain. You can still always

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Wed Jun 29 2016, Erica Sadun wrote: >> On Jun 29, 2016, at 3:59 PM, Xiaodi Wu via swift-evolution >> wrote: >> >> On Wed, Jun 29, 2016 at 4:50 PM, David Sweeris > > wrote: >> That’s the “as proposed” usage for

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Wed Jun 29 2016, David Sweeris wrote: > (While I was typing this up, I realized that the exact usage you’re > worried about, “MemoryLayout(Int.self).size” won’t compile, since > `MemoryLayout` currently doesn’t have instance properties. If you’re > worried about someone incorrectly typing

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

The only proposal that's in review is the one on github at Swift Evolution. I have been putting together another version as a courtesy for Dave A, to flesh out how the alternative approach would look if the alternative was the primary proposal. That one is a personal gist. -- E > On Jun 30,

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Good point; ideally, there would be no initializers at all. On Thu, Jun 30, 2016 at 10:24 AM, David Sweeris wrote: > Agreed. Also, if we’re supposed to say `MemoryLayout.of()` now, does > MemoryLayout still need a public init? Half of the proposal’s problems > revolve

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

As a meta-issue, it's been hard to make meaningful commentary during this review process because the latest proposal has been so rapidly shifting throughout. What, exactly, is the version we are reviewing at the moment? Can we have a few days to mull over that version specifically? On Thu, Jun 30,

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Agreed. Also, if we’re supposed to say `MemoryLayout.of()` now, does MemoryLayout still need a public init? Half of the proposal’s problems revolve around the likely-unexpected behavior caused by passing T.self to the init function (although, argument labels would also solve the issue). - Dave

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

I'm not sure this bikeshed is the right color yet. How does the user remember the distinction between MemoryLayout and MemoryLayout.of(Int) ? To keep it clear, how about ofValue() rather than of() ? Also, could the implementation be simply static func ofValue(_ value: @autoclosure () -> T)

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 29, 2016, at 3:59 PM, Xiaodi Wu via swift-evolution > wrote: > > On Wed, Jun 29, 2016 at 4:50 PM, David Sweeris > wrote: > That’s the “as proposed” usage for getting the size of a value (from >

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 29, 2016, at 4:59 PM, Xiaodi Wu wrote: > > There must be a typo in these examples. `MemoryLayout(x.dynamicType).size` > perhaps? Dunno if it’s intentional or not. Hooman Mehr already suggested we add instance properties: > On Jun 28, 2016, at 8:27 PM, Hooman

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

On Wed, Jun 29, 2016 at 4:50 PM, David Sweeris wrote: > That’s the “as proposed” usage for getting the size of a value (from > https://gist.github.com/erica/57a64163870486468180b8bab8a6294e) > > // Types > MemoryLayout.size // 8 > MemoryLayout.arraySpacing // 8 >

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

That’s the “as proposed” usage for getting the size of a value (from https://gist.github.com/erica/57a64163870486468180b8bab8a6294e) // Types MemoryLayout.size // 8 MemoryLayout.arraySpacing // 8 MemoryLayout.alignment // 8 // Value let x: UInt8 = 5 MemoryLayout(x).dynamicType.size // 1

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

On Wed, Jun 29, 2016 at 4:29 PM, David Sweeris via swift-evolution < swift-evolution@swift.org> wrote: > (While I was typing this up, I realized that the exact usage you’re > worried about, “MemoryLayout(Int.self).size” won’t compile, since > `MemoryLayout` currently doesn’t have instance

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

(While I was typing this up, I realized that the exact usage you’re worried about, “MemoryLayout(Int.self).size” won’t compile, since `MemoryLayout` currently doesn’t have instance properties. If you’re worried about someone incorrectly typing out “MemoryLayout(Int.self).dynamicType.size”,

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Wed Jun 29 2016, David Sweeris wrote: > Would adding a "init(_: T.self) {...}" solve that issue? > ? I don't see how. > > Sent from my iPhone > >> On Jun 29, 2016, at 01:54, Dave Abrahams via swift-evolution >> wrote: >> >> My worry is that people will write

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Would adding a "init(_: T.self) {...}" solve that issue? - Dave Sweeris Sent from my iPhone > On Jun 29, 2016, at 01:54, Dave Abrahams via swift-evolution > wrote: > > My worry is that people will write > > MemoryLayout(Int.self).size > > when they mean > >

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 28 2016, Hooman Mehr wrote: > How about we get rid of dynamicType by adding instance level properties as > well: > > public struct MemoryLayout { > > public static var size: Int { return sizeof(T) } > public static var interval: Int { return

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 28, 2016, at 6:08 PM, Dave Abrahams wrote: > -- > Dave Reload https://gist.github.com/erica/57a64163870486468180b8bab8a6294e and please make sure I properly updated the comments, the design, the examples. -- E ___

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Just wanting to point out that option 2 could look vastly different! Neither looks "pretty", but the first one sure looks good  Brandon > On Jun 28, 2016, at 8:08 PM, Dave Abrahams wrote: > > >> on Tue Jun 28 2016, Brandon Knope wrote: >> >> Isn't dynamicType

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 28 2016, Brandon Knope wrote: > Isn't dynamicType possibly changing soon to a method? A free function, I think. > This could look much different Yes, It will be uglier. But this very uncommon case is not important to optimize for beauty. -- Dave

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Isn't dynamicType possibly changing soon to a method? This could look much different Brandon > On Jun 28, 2016, at 4:53 PM, Erica Sadun via swift-evolution > wrote: > > On Jun 28, 2016, at 12:11 PM, Dave Abrahams via swift-evolution >

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

On Jun 28, 2016, at 12:11 PM, Dave Abrahams via swift-evolution wrote: >>> I think it would. It would *really* help if someone would prepare a >>> patch that uses both APIs so we could see how the resulting code looks >>> in practice. :-) >>> >>> -- >>> Dave >> >>

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Thu Jun 23 2016, Erica Sadun wrote: >> On Jun 22, 2016, at 1:32 PM, Dave Abrahams via swift-evolution >> wrote: >> >> >> on Wed Jun 22 2016, Erica Sadun wrote: > >> On Jun 22, 2016, at 11:51 AM, Dave

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Wed Jun 22 2016, Erica Sadun wrote: >> On Jun 22, 2016, at 11:51 AM, Dave Abrahams via swift-evolution >> wrote: >> >> >> on Wed Jun 22 2016, Erica Sadun wrote: >>> >>> No, I'd do edits on a gist page not

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 22, 2016, at 11:51 AM, Dave Abrahams via swift-evolution > wrote: > > > on Wed Jun 22 2016, Erica Sadun wrote: >> >> No, I'd do edits on a gist page not in-place > > Then feel free, of course! It's your choice, y'know. I

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Wed Jun 22 2016, Erica Sadun wrote: >> On Jun 21, 2016, at 7:07 PM, Dave Abrahams wrote: >> >> >> on Tue Jun 21 2016, Erica Sadun > > wrote: >> > On Jun 21, 2016, at 6:06 PM, Dave Abrahams

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 21, 2016, at 7:07 PM, Dave Abrahams wrote: > > > on Tue Jun 21 2016, Erica Sadun > wrote: > >>> On Jun 21, 2016, at 6:06 PM, Dave Abrahams wrote: >>> >>> It's just that I don't think this part of the

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> * What is your evaluation of the proposal? -1. I prefer the MemoryLayout struct approach that Dave Abrahams has suggested. The proposed names retain the the disadvantage of several top level names and introduce a new disadvantage that they are not directly related to familiar terms

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

+1 to MemoryLayout, as I do like how it is namespaced under one type, which allows straight forward looking up of documentation. Writers from C or other sizeof() languages will able to see all available methods, allowing them to be educated to say not go for size but interval/spacing as the

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 21 2016, Erica Sadun wrote: >> On Jun 21, 2016, at 6:06 PM, Dave Abrahams wrote: >> >> It's just that I don't think this part of the library API is important >> enough, to enough people, that this readability is worth the additional >> exposed surface area (and

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 21, 2016, at 6:06 PM, Dave Abrahams wrote: > > It's just that I don't think this part of the library API is important > enough, to enough people, that this readability is worth the additional > exposed surface area (and further exposure later on—I can easily

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> * What is your evaluation of the proposal? Generally in support, with two small exceptions: 1. I think the type variants should have the parameter label `of`. `memorySize(of: Int.self)` reads grammatically (other than the hopefully soon-to-be-vestigial `self`); `memorySize(Int.self)`

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 21 2016, Erica Sadun wrote: >> On Jun 21, 2016, at 3:02 PM, Dave Abrahams via swift-evolution >> wrote: >> >> If I didn't think it would produce semantic confusion, these would be >> static members e.g. `Array.memoryAlignment`, and you'd have to “scan >>

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 21, 2016, at 3:02 PM, Dave Abrahams via swift-evolution > wrote: > > If I didn't think it would produce semantic confusion, these would be > static members e.g. `Array.memoryAlignment`, and you'd have to “scan > past” `Array`. It's a perfectly natural way

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 21, 2016, at 1:23 PM, Dave Abrahams wrote: > > > > > on Tue Jun 21 2016, Joe Groff > wrote: > >> Regarding the issue of existential metatypes with sizeof: >> >> Pyry Jahkola points out one instance

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 21 2016, Joe Groff wrote: > Regarding the issue of existential metatypes with sizeof: > > Pyry Jahkola points out one instance where the memorySize(type(of: …)) > workaround won't work. When the value is an existential, it's

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 21 2016, Erica Sadun wrote: >> On Jun 21, 2016, at 2:36 PM, Dave Abrahams wrote: >> >> >> on Tue Jun 21 2016, Erica Sadun > > wrote: >> > On Jun 21, 2016, at 12:45 PM, Joe Groff via

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 21, 2016, at 2:36 PM, Dave Abrahams wrote: > > > on Tue Jun 21 2016, Erica Sadun > wrote: > >>> On Jun 21, 2016, at 12:45 PM, Joe Groff via swift-evolution >>> wrote: >>> This could be enabled by

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

on Tue Jun 21 2016, Erica Sadun wrote: >> On Jun 21, 2016, at 12:45 PM, Joe Groff via swift-evolution >> wrote: >> >> Regarding the issue of existential metatypes with sizeof: >> >> Pyry Jahkola points out one instance where the memorySize(type(of: > >> …))

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

> On Jun 21, 2016, at 12:45 PM, Joe Groff via swift-evolution > wrote: > > Regarding the issue of existential metatypes with sizeof: > > Pyry Jahkola points out one instance where the memorySize(type(of: …)) > workaround won't work. When the value is an

Re: [swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

On 21 June 2016 at 14:03, Chris Lattner via swift-evolution wrote: > Hello Swift community, > > The review of "SE-0101: Rename sizeof and related functions to comply with > API Guidelines" begins now and runs through June 27. The proposal is > available here: > >

[swift-evolution] [Review] SE-0101: Rename sizeof and related functions to comply with API Guidelines

Hello Swift community, The review of "SE-0101: Rename sizeof and related functions to comply with API Guidelines" begins now and runs through June 27. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/proposals/0101-standardizing-sizeof-naming.md