5 ms·
Implemented proposals for Swift 3
- kinofcain 11y agoOne thing I don't see in this list (though maybe I'm missing it) is the ability to expose a Swift function as a function compatible with the C ABI. Something like extern "C" in C++ or no_mangle in Rust. You can pass @convention(c) blocks around as C function pointers, but you can't currently call directly into a Swift library from C code. That makes it difficult to do things like expose platform-specific functionality to a shared C library using Swift. Right now you have to implement the C function inside an Objective-C file, and then have your Objective-C code call your Swift code, or you have to change all your interfaces to allow injection of function pointers for all external dependencies. It's the kind of thing that makes staying with Objective-C attractive for that type of stuff, but Swift in general has been a solid improvement, and I'd like to not have to give that up.
- musesum 11y agoYes, I was hoping that 3.0 would allow C++ and Swift to call each other. Have spent a few thousand hours writing a reactive ontology in C++ that currently calls to and from ObjC. I was asking about C++ support in the WWDC 2015 labs, and the answer was using an ObjC wrapper workaround. As a result, I put off a major port for "next year".
- justsaysmthng 11y agoFrom https://github.com/apple/swift-evolution https://github.com/apple/swift-evolution " ... However, C++ itself is a very complex language, and providing good interoperability with C++ is a significant undertaking that is out of scope for Swift 3.0. "
- stevetrewick 11y agoSeems to be being worked on, an attribute @_cdecl has been merged into master [0] and seems to compile in the current beta of 3.0 [1] although I haven't tested it. [0] https://github.com/apple/swift/commit/013aad13d4245a012cfb762b7edccf92013b3609 https://github.com/apple/swift/commit/013aad13d4245a012cfb76... [1] http://swiftlang.ng.bluemix.net/#/repl/d68be430e72609717f718006aa0ae137eae872ca7a0b7e8141b351770b0c9eac http://swiftlang.ng.bluemix.net/#/repl/d68be430e72609717f718...
- kinofcain 11y agoAwesome, thanks so much for pointing that out.
- stevetrewick 11y agoYou're welcome. I have a custom mouse cursor a11y app that has to use some nasty old C callback API, which is exactly the PITA you describe, so I've been keeping an eye out.
- mmastrac 11y agoI'm surprised they removed x++ from the language. This is always a big frustration when I'm writing Python code.
- kinofcain 11y agoRust did too. There's probably a pie chart somewhere of time lost to having to type out "foo += 1" vs number of hours lost to people screwing up operator precedence for foo++ or ++foo. (EDIT: as munificent points out this is actually a combination of operator precedence and sequence points) The pie chart is probably severely lopsided. EDIT: Since the main problem is the precedence of the post increment/decrement operator, I would have preferred to see them get rid of that one and keep ++foo but overall not much of a loss. At least they didn't get rid of the ternary operator like Go did...
- mmastrac 11y agoIf anything it would be time lost to accidentally typing ++x instead of x++. I always found the precedence to be pretty intuitive in C (unary ops generally bind tightest). The only time you'd have to Google is if you were doing something weird like `-(x++)`. I'm also willing to accept that I'm old, stubborn, and unhappy about changing my ways and that this is the future... :)
- kinofcain 11y agoSee I always thought most people who wrote foo++ actually meant ++foo and it typically only came up when the operator precedence made the two not equivalent, causing a subtle bug. I can't even think of a time where I really needed a use-then-increment operator where I wouldn't have just used the value, then incremented it on the next line anyway (maybe even with a post-increment out of habit).
- mmastrac 11y agoInteresting. I generally choose x++ for the majority of array-striding code I write, and usually as a shortcut to avoid having a bunch of x++ lines scattered around. I've found that you can structure your code either way and postfix seems to be easier to reason over for me. I use ++x very infrequently, and mainly in hand-written text parsers.
- thurn 11y agoStill no way to export structs or enum-ADTs to Objective C code, though. Really makes it hard to write idiomatic Swift APIs that can be called from Objective C.
- pjmlp 11y agoGiven the legacy status of Objective-C, when does such use case matter? The way forward is to call existing Objective-C from new Swift code. The only WWDC talks with Objective-C code were related to the new features to make Objective-C easier to call from Swift.
- Negative1 11y agoCurious; have they made any statements on their versioning? I've seen mature projects years in development that are still 0 for major and in the teens for the minor version. Despite breaking changes Swift is now a 3.0 project?
- AsyncAwait 11y agoI've come to the conclusion that is because Apple can't release anything that may not look (on paper) as being "ready", since they built their image on attention to detail and polished products - so in other words, a Swift 0.x. would not have seem polished/professional enough for Apple to release into the wild, even if it had all the present functionality.
- natthan 11y agoI believe that they are using Semantic Versioning 2.0.0[1] as discussed in the Swift Package Manager Project's Website[2] under "Importing Dependencies": > Given a version number MAJOR.MINOR.PATCH, increment the: > MAJOR version when you make incompatible API changes, > MINOR version when you add functionality in a backwards-compatible manner, and > PATCH version when you make backwards-compatible bug fixes. > Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. [1] Semantic Versioning 2.0.0 http://semver.org http://semver.org [2] Swift.org - Package Manager https://swift.org/package-manager/ https://swift.org/package-manager/
- deleted 11y ago[deleted]
- paxcoder 11y agoLet me guess: It's not a complete standard library?
- valleyer 11y agoThey have publicly said that they want to keep the standard library small, and swift-corelibs-foundation is available and open-source.
- paxcoder 11y agoIt is incomplete: https://github.com/apple/swift-corelibs-foundation/search?utf8=%E2%9C%93&q=NSUnimplemented%28%29 https://github.com/apple/swift-corelibs-foundation/search?ut...
- orbitur 11y agoHow do we get to the PRs/commits for the proposals? I see a link to a JIRA issue, but the issue doesn't link to anything in Github.
- jayrhynas 11y agoThis gets you pretty close: https://github.com/apple/swift/pulls?q=is%3Apr+SE- https://github.com/apple/swift/pulls?q=is%3Apr+SE-