[swift-evolution] SE-0025: Scoped Access Level, next

[David Hart]

I’m fairly sure what you are asking for already exists with @testable: https://www.natashatherobot.com/swift-2-xcode-7-unit-testing-access/

> On 01 Apr 2016, at 23:04, John Heerema via swift-evolution <swift-evolution at swift.org> wrote:
> 
> I’m a fan of test-driven development.
> I use it myself, and teach it to students and colleagues.
> 
> One of the nice things about Swift 1.0 was that it was easy to write module tests.
> 
> When access controls were introduced into Swift, I found that many functions and objects that had no genuine need to be public, suddenly had to become public in order to be tested. That just seems wrong to me.
> 
> I’d like to see a way for tests, which are not normally part of the module, to have access to a module’s contents (I’m talking source only – not packages that do not include source). That might simply be a feature of the IDE, rather than a language feature.
> 
> On another note, I see “file private” (whatever it’s called) as a legacy of C. I have trouble seeing it as being truly useful, but can see that others might have genuine uses for it (actually, I’d like to hear what they might be)
> 
> Thanks,
> Dr. J. Heerema 
> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution