Re: [swift-evolution] [discussion] SPI?

Could you clarify? What do you hope to achieve beyond access/visibility control? > Le 14 août 2017 à 07:19, Mathew Huusko V via swift-evolution > a écrit : > > Curious if SPI access/visibility control has been discussed/planned? I know > the standard access control

Re: [swift-evolution] Swift source mentorship program

I think that "we don't have time to implement this time-saving project-accelerating quality-improving thing" is widely recognised as an anti-pattern (or anti-process if that’s a thing) these days, and I’d hope Apple would find a way to avoid this problem. :) ​ On Mon, 14 Aug 2017 at 21:44 Jacob

Re: [swift-evolution] Swift source mentorship program

A Swift developer has actually started a blog series about the swift compiler. The links to his post were posted in one of the evolution topics a little while ago. The series is incomplete, but it gives a lot of explanations about the various parts of the swift compiler.

[swift-evolution] Swift source mentorship program

I think we should have some kind of mentorship program for the swift source. I'm confident that my following statement doesn't apply to just me: "I'd love to get involved in the source a lot more, and my previous efforts to browse around and understand it a bit better have been thwarted by lack

Re: [swift-evolution] "layoutSubviews()" and "layoutIfNeeded()" camel casing mistake

> On 14 Aug 2017, at 17:12, Matthias Heymann via swift-evolution > wrote: > > Hi, > > I noticed that strictly speaking, the camel casing of methods like > “layoutSubviews()” and "layoutIfNeeded()" in the UIView class is wrong: The terminology comes from UIView,

Re: [swift-evolution] "layoutSubviews()" and "layoutIfNeeded()" camel casing mistake

Hi Matthias, UIKit is not part of Swift - it's maintained by Apple. You may file a bug report at bugreport.apple.com , but my guess is that the chances that this will change are very slim. > On Aug 14, 2017, at 6:11 PM, Matthias Heymann via swift-evolution >

[swift-evolution] "layoutSubviews()" and "layoutIfNeeded()" camel casing mistake

Hi, I noticed that strictly speaking, the camel casing of methods like “layoutSubviews()” and "layoutIfNeeded()" in the UIView class is wrong: Clearly, the word “layout” is used as a verb here and should therefore be spelled as TWO words, as in “please lay out all subviews”. Only the noun form

[swift-evolution] [discussion] SPI?

Curious if SPI access/visibility control has been discussed/planned? I know the standard access control debate is long past, but this still seams rather important, especially for stdlib (and would presumably have ABI implications) and other large frameworks.