News for hackers. Stuff that matters.
Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @10:17AM (#12581959)
Speaking only for myself, avoiding or breaking retain cycles is a noticeable problem in Swift code that simply isn't there in languages with a proper garbage collector. Among newer iOS programmers, it's a big point of confusion to figure out when a callback closure should use [weak self] versus capturing self strongly, for example. I've seen a lot of people struggle to understand, completely fail, and end up dogmatically using [weak self] everywhere whether it's needed or not (and sometimes where it's actually harmful).
Re:IBM says Swift is ready for the enterprise by stepanhruda on Monday September 26, 2016 @11:26AM (#12582606)
With @nonescaping becoming the default, this might become a bit simpler. Not too much, but a bit.
Re:IBM says Swift is ready for the enterprise by pjmlp on Monday September 26, 2016 @10:38AM (#12582170)
It is much easier than in either C++ or Rust.
Re:IBM says Swift is ready for the enterprise by pcwalton on Monday September 26, 2016 @11:52AM (#12582842)
Technically true, but very misleading in Rust's case. In Rust you rarely have to break retain cycles in the first place, simply because you don't use reference counting much. Things like "weak self" are not a problem, because closures aren't reference counted unless you explicitly make them so (and in fact I don't think I've ever seen a reference counted closure in practice).
Re:IBM says Swift is ready for the enterprise by pjmlp on Monday September 26, 2016 @12:24PM (#12583179)
I agree.

I only mentioned Rust, because of ergonomics, since the compiler cannot guide the user unless the types are known.

Or is already something in place to make use of intrisics for better error messages in such cases, instead of just giving a type error?

Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @10:52AM (#12582291)
Don't C++ and Rust offer the same facilities? C++ has std::weak_ptr and Rust has std::rc::Weak.
Re:IBM says Swift is ready for the enterprise by pjmlp on Monday September 26, 2016 @11:01AM (#12582370)
Yes, but they are library calls without any help from the compiler.
Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @11:11AM (#12582464)
How does that make them any more difficult to use?
Re:IBM says Swift is ready for the enterprise by pjmlp on Monday September 26, 2016 @12:21PM (#12583139)
The compiler can provide better error messages and guide the user, whereas with library types, at least on C++'s case it requires help from external tooling.

With Rust, while you can make use of the type system, it is harder for the compiler to provide such guidance, unless the types are somehow blessed.

Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @12:46PM (#12583388)
What sort of guidance does Swift provide here? And nothing prevents Rust or C++ compilers from becoming aware of these types and providing specialized diagnostics for them.
Re:IBM says Swift is ready for the enterprise by pjmlp on Monday September 26, 2016 @02:13PM (#12584191)
I said it can, not that it does it already.

My Swift experience is constrained to the GNU/Linux version, so I don't know if XCode is already doing something in this direction.

Sure one can have blessed library types that the compiler knows about, but then from language design point of view it creates a decision between those types and others written by developers, but with similar semantics.

Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @02:47PM (#12584501)
Since you said it's easier than these other languages, I thought you were referring to how the languages work now.

There's nothing wrong with special treatment for stuff in the standard library. C and C++ already do this with many things (e.g. many compilers understand calls like memcpy and will emit optimized code based on the standard library semantics) and Swift gives special treatment to built-in types like Optional.

The distinction here is fairly blurred. The Swift implementation of weak pointers is mostly in the runtime library already, it's just that the compiler hides it a bit so you don't write the names of the calls directly.

Re:IBM says Swift is ready for the enterprise by pjmlp on Monday September 26, 2016 @04:13PM (#12585156)
Sure, I was more thinking about the language geek point of view.

Thanks for clarifying.

Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @04:59PM (#12585497)
Understood. If you have any ideas for cool diagnostics or other guides, I'd be interested in hearing. I couldn't think of anything offhand, but that's probably just my lack of imagination. I would love to see some static analysis help for finding retain cycles and recommending how to break them, but I'm not sure if that's practical.
Re:IBM says Swift is ready for the enterprise by fauigerzigerk on Monday September 26, 2016 @11:27AM (#12582608)
You have to manually optimize away unnecessary reference counting without help from the compiler.
Re:IBM says Swift is ready for the enterprise by pcwalton on Monday September 26, 2016 @11:50AM (#12582823)
I have never seen unnecessary reference counting be a problem in Rust. That's because not manipulating the reference count requires an explicit action—.clone()—and borrowing is so expressive that you rarely need to manipulate the counts.
Re:IBM says Swift is ready for the enterprise by fauigerzigerk on Monday September 26, 2016 @12:18PM (#12583103)
I guess that's because in Rust you never need defensive reference counting thanks to the borrow checker.
Re:IBM says Swift is ready for the enterprise by Rusky on Monday September 26, 2016 @01:02PM (#12583518)
Rust's borrow checker actually helps with this a lot- you can hand out references to the Rc-ed data without modifying the count, and the compiler will enforce that the count is not decremented until the references are dead. Combined with the fact that plain references are more idiomatic than Rc/Arc, this leads to pretty similar results.
Re:IBM says Swift is ready for the enterprise by mikeash on Monday September 26, 2016 @11:39AM (#12582719)
That is true, but a totally different issue from breaking or avoiding retain cycles.