Derrick and Jean-Daniel, it's my understanding that Benjamin is proposing
adding a way *to test that members are private/internal/public*, not a way to
access private members in tests. If you'd like to discuss what you're
describing, it's probably best to start a separate email thread.
- Brian
Hi Benjamin,
I think your proposal is interesting, and you're certainly right: XCTest
has no way to test accessibility levels, or the other attributes you
mention. However, I wonder, what do you hope to achieve by adding an
automated test for accessibility levels?
Maybe your goal is to verify
Apologies if this was announced elsewhere: is commit access to master
restricted?
I noticed I couldn't merge some documentation improvements in
https://github.com/apple/swift/pull/3815, and just wanted to make sure this
was due to Swift 3 finalization.
If commit access is restricted, is it safe
ever adopted modules. Given that they just got punted
>> from C++17, though, maybe that shouldn't hold us back.
>>
>> Jordan
>>
>>
>> On Mar 8, 2016, at 11:13, Brian Gesiak via swift-evolution <
>> swift-evolution@swift.org> wrote:
>>
>> # Int
