Re: [swift-users] [swift-corelibs-dev] Building swift with xctest and foundation fails

Hi Philippe, That doesn't solve the issue either! Cheers! Mohit On Wed, Mar 29, 2017 at 7:21 PM, Philippe Hausler wrote: > You need to also pass --libdispatch but I am not quite sure that will > fully fix the problem at hand. > > Sent from my iPhone > > On Mar 29, 2017, at 6:29 PM, Mohit Athw

Re: [swift-users] [swift-corelibs-dev] Building swift with xctest and foundation fails

You need to also pass --libdispatch but I am not quite sure that will fully fix the problem at hand. Sent from my iPhone > On Mar 29, 2017, at 6:29 PM, Mohit Athwani via swift-corelibs-dev > wrote: > > I'm trying to get back to work starting from scratch on Swift Foundation on > my Ubuntu 16

Re: [swift-users] Forward Class Declaration in Swift...

The compiler (in a way) has whole module visibility and cross module visibility when importing modules. No need exists for such a thing as a result. -Shawn On Wed, Mar 29, 2017 at 6:31 PM Peters, Brandon via swift-users < swift-users@swift.org> wrote: > Is it possible to do forward class declara

[swift-users] Forward Class Declaration in Swift...

Is it possible to do forward class declaration in Swift similar to C++? ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users

[swift-users] Building swift with xctest and foundation fails

I'm trying to get back to work starting from scratch on Swift Foundation on my Ubuntu 16.04 LTS system. I cloned the main swift repo and all of it's dependencies via ssh ./swift/utils/update-checkout --clone-with-ssh and after running (taken from instructions from the Foundation site): swift/ut

Re: [swift-users] Set with element of NSObject subclasses didn't work as expected

I dropped two words in my initial sentence. The complete sentence is: We need further emphasis and clarification in the documentation for people who are starting Apple development with Swift with no prior knowledge of ObjC/NSObject stuff. > On Mar 29, 2017, at 11:40 AM, Hooman Mehr via swift-us

Re: [swift-users] [swift-build-dev] Importing C system libraries

Yep, we need to have better support for system packages. Unfortunately it is not covered in the Swift 4 Package Manager roadmap , but community driven proposal are always welcomed! > On 30-Mar-2017, at 12:25 AM

Re: [swift-users] [swift-build-dev] Importing C system libraries

I agree that portability is valuable and that it’s something that’s lacking in the c/makefile workflow. I just don’t think empty git repositories are the right solution. Perhaps we can get the best of both worlds with something like this in the SwiftPM: .Package(include: "cairo.h", link: "cai

Re: [swift-users] Set with element of NSObject subclasses didn't work as expected

> On Mar 29, 2017, at 11:36 AM, Joe Groff via swift-users > wrote: > > Perhaps the NSObject implementation of `hashValue` should be final to help > with this. Good idea. And as I mentioned in my other reply, we need further emphasis and clarification in the documentation who are starting Ap

Re: [swift-users] Set with element of NSObject subclasses didn't work as expected

> On Mar 28, 2017, at 12:50 PM, Zhao Xin via swift-users > wrote: > > Please see the code first. > > import Foundation > > class Foo:Hashable { > let value:Int > > public var hashValue: Int { return value } > public static func ==(lhs: Foo, rhs: Foo) -> Bool { > retur

Re: [swift-users] [swift-build-dev] Importing C system libraries

I agree that libressl isn't a good example because of the security questions it raises, but libYAML is a good self contained package IMO. With custom targets layout proposal, the forks can be replaced by submodules. The problem with apt-get approach is, it takes away the "portability" from the p

Re: [swift-users] [swift-build-dev] Importing C system libraries

Given the effort behind wrapping all of the functionality in swift package manager into an API (libPackageManager) so that in the future it can be used by IDE style tools, I don't think you need to be seriously concerned. It's convenient for the swift package folks, especially while supporting L

Re: [swift-users] [swift-build-dev] Importing C system libraries

I don’t think this is a good approach, the libressl repo is pretty much just the source code of the C library copied and pasted into a Swift module. That’s not a good thing™. The linux build paradigm is, the library maintains its own *official* source repository

Re: [swift-users] Set with element of NSObject subclasses didn't work as expected

Yes, this is a serious shortcoming in the transition to Swift as the main application programming language for Apple platforms. With the existing architecture (lack of stable Swift ABI) system frameworks and any binary distributed frameworks still have to be written in Objective-C. If you are a

Re: [swift-users] Set with element of NSObject subclasses didn't work as expected

Now I understand it. What I don't understand is why there is nowhere metioning this. All docs are talking about Hashable, clearly that NSObject didn't rely on it. Zhaoxin Get Outlook for iOS From: Saagar Jha Sent: Wednesday, March 29, 201