News for hackers. Stuff that matters.
Re:Swift 3.0 Release Process by yokohummer7 on Saturday May 07, 2016 @07:38AM (#11649202)
> It looks like a really well thought out language

Well, I think it could have been more cleanly designed if it was able to abandon the burden of Objective-C interoperability. (But Apple can't do this, obviously.) The standard libraries could have also been much cleaner if it didn't rely on NextStep. Also, I don't personally like the dichotomy of value types and reference types, but YMMV.

Re:Swift 3.0 Release Process by cies on Saturday May 07, 2016 @08:04AM (#11649267)
You say

> it could have been more cleanly designed if it was able to abandon the burden of Objective-C interoperability

You mean this for the language itself and not the (standard) libraries; right?

> The standard libraries could have also been much cleaner if it didn't rely on NextStep.

I agree.

Re:Swift 3.0 Release Process by TillE on Saturday May 07, 2016 @09:41AM (#11649546)
There are at least a few aspects of the language (eg, the special case for the first argument passed to a method) which would be completely bizarre decisions if not for the Objective-C compatibility requirements. Though I think they're tweaking that a bit.
Re:Swift 3.0 Release Process by donut2d on Saturday May 07, 2016 @11:05AM (#11649842)
> special case for the first argument passed to a method

Are you talking about the weirdness where the first argument doesn't require a label? If so, that decision has been made explicit in the last few dev snapshots of 3.0. Basically, if you don't want to require a label when call a function/method then it must be made explicit.