<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I’m a fan of test-driven development.</div>
<div>I use it myself, and teach it to students and colleagues.</div>
<div><br>
</div>
<div>One of the nice things about Swift 1.0 was that it was easy to write module tests.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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)</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Dr. J. Heerema </div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>