Recent contacts bad. Searching for the big idea behind the little Apple Watch By E. Kinetics: pretty puzzler without much grit By E. Gold: The secret shame of my late night iPhone order By E. Doing the math: Apple device pixels on parade By E. Hands on with Voice Dream's ebook narration By E.
HWS: Do you have any simple suggestions for folks who are thinking of joining in — is it perhaps a matter of just picking and choosing the proposals that interest you most?
Just filing a bug report is joining in, whether it is for a feature you want in the language or a performance issue or whatever. ES: I know many developers, for example, who refuse to file bug reports into Apple's "radar" system. You can see a bug's progress, comment on it, discuss it with the language maintainers. Yes, just pick and choose the proposals that interest you the most.
It's low volume and lets you know about review periods, acceptances, rejections, and returns for revisions. HWS: Looking at the list of changes for 4. What are the major areas where you think the language is still lacking? So yes, there's quite the rush going on.
From here out, what you'll see is more additions to other libraries like Foundation instead of the standard library. And there will be a lot of work under the hood to make the language more stable, faster to compile, and so forth. New proposals cannot break code.
And those changes must fix real problems, not theoretical ones. Swift Evolution is entirely a user-facing process. Anything that affects the way that users interact with the language must go through the Swift Evolution process. Currently, any language changes must be highly focused with limited impact.
Their benefits, if accepted, must be measurable and real. Changes must fix real problems, not theoretical ones. So you can't add many 'good ideas' to the language. This is, of course, where I worried about toggle. The problem it fixes is real a mutating, functional way to toggle a boolean value in place but I wasn't sure at first that its impact was sufficient.
Finally, changes to the language must directly improve safety, speed, and expression. The toggle proposal fell into the last of these. ES: It certainly changed the way Swift Evolution did business, and it was pretty much down to me why they did this.
The proposal extend Self to classes the way it works in Objective-C, where Self is the type and self is the current instance. As of right now, no one has been able to make that work. The rule that was introduced ensures that proposal are not just real problems, they are ones that are solvable. You need an implementation, which allows designs to be tweaked and road-tested,. ES: It is. And I am slowly learning both. I feel it is important to be able to contribute at a code level not just ideas and write-ups.
ES: That is actually not a problem at all. The people on the swift-dev side of the house are amazingly supportive, especially of beginners. They even publish "starter bugs" for people who want to become more active in language development. It's also an extremely good way to get a job at Apple, should you follow that path.
ES: I mean this seriously when I say the entire Swift-Dev community is filled with love, unicorns, happiness, and lollipops. Swift Evolution tends to be a little bit more thorny but also full of wonderful people.
They're just crankier unicorns and pickier lollipops. What do you think truly idiomatic Swift looks like, if such a thing can even really exist this early in a language? ES: I honestly think that Swift looks a lot like nearly every other modern language.
They're all kind of converging right now. Feature by feature, you talk to people, and they'll point out correspondences in 2, 3, or even more languages. Swift benefits by trailing slightly and learning important lessons. Issues with protocol extensions may have already been hashed out in C.
Or you might have already seen raw strings in Python. Following on makes it easier to accommodate already road-tested ideas and enhance development. I know that I personally want method cascades like you get in Dart.
A method cascade avoids those blocky setup columns of doom, making it clear that you're establishing a single object's properties outside of initializers. ES: It really depends on how recently I've been in that or another language. Start Reading. Sign up now Website. Add a rating for this content Sign in to add a rating. All videos. All books. One low price. Learn more. Mark Complete Clear Progress. Even though Marco began his career at Tumblr, he is mostly known for Instapaper and Overcast.
Aaron is a veteran in the Cocoa community. He founded Big Nerd Ranch fifteen years ago and has written severals books about Cocoa development. On the interwebs, Natasha is better known as Natasha The Robot.
She has been writing about Swift ever since the language was introduced in
0コメント