[swift-evolution] [Review] Require self for accessing instance members
nickmshelley at gmail.com
Wed Dec 16 14:43:59 CST 2015
> I doubt that the one-sided argument in the proposal was blatant.
I should not have called it blatant, I'm sorry I rashly attributed intent.
The fact is that the current proposal is one-sided (regardless of intent),
and it seems like many in the community (including the author) are unsure
whether and when a proposal should be updated and what its actual role is
in the review process.
I would like to take back any accusations I may have made and simply ask
for clarification about the role and lifecycle of a proposal.
On Wed, Dec 16, 2015 at 1:32 PM, Dan Loewenherz <dan at lionheartsw.com> wrote:
> It’s my understanding that the proposal itself is just a starting
> point. I do believe that the reviewers will review all commentary from
> the mailing list in addition to direct commentary. I doubt that the
> one-sided argument in the proposal was blatant; undoubtedly, the Swift
> team has been inundated with work and merging PR #59 fell by the
> wayside. I’m sure everyone’s arguments for and against will be
> considered and reviewed. The team has proven many times that they are
> thoughtful in their decision-making process.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution