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

2017-08-15 Thread Mathew Huusko V via swift-evolution
It looks like a `hidden` access control has been discussed before: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170213/031881.html Not directly related, but would serve a similar purpose. I'm fairly sure whether it's revisiting protected, or something like 'hidden' with special

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

2017-08-15 Thread Mathew Huusko V via swift-evolution
Yes, sorry. First and foremost I'm referencing SPI access control as mentioned in https://github.com/apple/swift/blob/master/docs/LibraryEvolution.rst#backdating, https://github.com/apple/swift/blob/master/docs/AccessControlInStdlib.rst#public , https://github.com/apple/swift/blob/master/docs/Acces

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

2017-08-14 Thread Félix Cloutier via swift-evolution
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 debate is long past, but thi

[swift-evolution] [discussion] SPI?

2017-08-14 Thread Mathew Huusko V via swift-evolution
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.