Maybe this is the core of this whole issue. In my experience, the very
easiest part of the software development process is getting it to compile.
The *real effort* doesn't even start until after that's completed.
If I thought that "case-sensitive find-and-relace" was "the tricky thing"
in developing software, and all I had to care about was avoiding "invalid
redeclarations anywhere" then this proposal might seem like a good idea to
me, too.
-Carl
From: Xiaodi Wu via swift-evolution <swift-evolution@swift.org>
To: Drew Crawford <d...@sealedabstract.com>, Jonathan Hull
<jh...@gbis.com>
Cc: swift-evolution <swift-evolution@swift.org>
Date: 03/24/2017 11:10 PM
Subject: Re: [swift-evolution] [Review] SE-0159: Fix Private Access
Levels
Sent by: swift-evolution-boun...@swift.org
On Fri, Mar 24, 2017 at 10:47 PM, Xiaodi Wu <xiaodi...@gmail.com> wrote:
Update: with the caveat that corelibs-foundation tests are incomplete, it
took me about 15 mins to migrate all uses of private to fileprivate. The
tricky thing is that one has to do case-sensitive find-and-replace, and to
replace all instances of "filefileprivate" in a second round. It does not
appear that corelibs-foundation actually uses new `private` in a way that
migrating to `fileprivate` results in invalid redeclarations anywhere.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
