Please provide draft document and then ask for review about swift-style-guide HOT 6 CLOSED

👍

from swift-style-guide.

Personally I have been finding the process of debate quite useful and have learnt (Ooops @eskerber I mean learned!) a few things along the way as a result.

I have been creating Pull Requests with new sections at a rate of about one a day when I see a rough consensus in a topic.

If you are not enjoying the discussion, then why not sit back and wait for the document to become more complete?

Anyhow, @gregheo is in 'charge' of this style guide, but it is really a team effort.

from swift-style-guide.

I was planning on letting the discussion go for a week or so and then do some writing/pull requests to garner more comments but @ColinEberhardt is way ahead of me. Yeah, I've been slacking a bit ;]

from swift-style-guide.

The reason I can't "sit back and wait" is because then you'll write it up and at that point a dissenting opinion won't mean much because "we already discussed this and came to a consensus". By writing it first and then discussing, much of this would be unnecessary because the obvious choice would already be in place.

For example:

Swift has let and var, and the compiler optimizes for let. Please debate which to use.
Names can either be descriptive or not. Thoughts?
This is a Swift style guide. How about we prefer types from Obj-C over Swift types?

There are certainly some areas where discussion helps, like closure syntax because it's new and there is no "correct" way to do it. But much of this could have been written up without a moment's thought and no one would have questioned it.

Also, please remember that this guide is first and foremost for the authors who are writing the books. We can certainly tweak things later, but authors are already working on their chapters and as of yet we haven't decided what even the most basic code should look like.

--------- Original Message --------- Subject: Re: [swift-style-guide] Please provide draft document and then ask for review (#29)
From: "ColinEberhardt" [email protected]
Date: 6/20/14 1:22 am
To: "raywenderlich/swift-style-guide" [email protected]
Cc: "elephantronic" [email protected]

Personally I have been finding the process of debate quite useful and have learnt (Ooops @eskerber I mean learned!) a few things along the way as a result.
I have been creating Pull Requests with new sections at a rate of about one a day when I see a rough consensus in a topic.
If you are not enjoying the discussion, then why not sit back and wait for the document to become more complete?
Anyhow, @gregheo is in 'charge' of this style guide, but it is really a team effort.

Reply to this email directly or view it on GitHub.

from swift-style-guide.

For the more obvious sections, you, or anyone else, would be most welcome to contribute this. It would be very much appreciated!

from swift-style-guide.

OK, I'm trying to clear out some issues that have died down. I'm sure there will still be discussion and debate so let's keep that up!

from swift-style-guide.