[swift-users] Swift and Xcode along with Playgrounds is full of bugs

Shyamal Chandra shyamalc at gmail.com
Mon Sep 12 17:32:06 CDT 2016

Hi Jens and mailing list members,

I hope that Chris Lattner and the Swift team can move to that goal very
quickly by following the trend of Go and Rust that have already gone
through that process.  Most of the documentation from different publishers
is going to be outdated very quickly if the syntax and semantics change
significantly.  I hope that the Swift open source team, even outside of
Apple Inc., can come up with an actively added documentation that has
recipes for all the function calls for all the libraries that is constantly
evolving as the language changes with testing done by Jenkins-like server.
  That would be very helpful for developers who need an ever-changing
technical documentation resource for an ever-changing and evolving language.



Shyamal Chandra
shyamalc at gmail.com
Linkedin: http://www.linkedin.com/in/shyamalc
Phone: 620-719-9064

On Mon, Sep 12, 2016 at 5:21 PM, Jens Alfke <jens at mooseyard.com> wrote:

> On Sep 12, 2016, at 3:03 PM, Shyamal Chandra via swift-users <
> swift-users at swift.org> wrote:
> Instead of moving onto Swift 3, 4, and 5 (with different syntax), why
> don't you standardize the library and language operations and functions for
> the different package and frameworks included with Xcode
> That is the goal, and apparently it will happen with Swift 4. It’s a very
> large goal, and if you wanted the Swift designers to hold off on releases
> until it was complete, there’d be no updates to the language for some time.
> Moreover, outside developers would have no input into the changes going on,
> unlike the current development process where anyone can suggest and discuss
> proposals.
> Other new languages like Go and Rust have also gone through years of early
> evolution where syntax and APIs changed incompatibly. (In the case of Go,
> it happened prior to 1.0 when hardly anyone was paying attention to it.)
> —Jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20160912/987eb996/attachment.html>

More information about the swift-users mailing list