Re: [swift-users] Ugliness bridging Swift String to char *

2017-03-05 Thread Kenny Leung via swift-users
Follow-up on this: The StaticString solution doesn’t work: let separator: StaticString = “|” opt.fieldSep = UnsafeMutablePointer(mutating: separator.utf8start) … because utf8start returns UnsafePointer, and fieldSep is actually UnsafeMutablePointer. There doesn’t seem to be any way to convert

[swift-users] TWISt-shout Newsletter 2017-03-06

2017-03-05 Thread Kenny Leung via swift-users
Hi All. Here is your TWISt-shout Newsletter for the week of 2017-02-27 to 2017-03-05 https://github.com/pepperdog/TWISt-shout/blob/master/2017/TWISt-shout-2017-03-06.md Enjoy! -Kenny ___ swift-users mailing list swift-users@swift.org

Re: [swift-users] Anyone else having trouble getting swift to build?

2017-03-05 Thread Jacob Bandes-Storch via swift-users
Shot in the dark: are you using the latest Xcode beta? On Sun, Mar 5, 2017 at 3:03 PM, David Sweeris via swift-users < swift-users@swift.org> wrote: > In particular, the "utils/build-script -x” will fail with 84 errors on my > system. As best as I can tell, they're all/mostly linker errors

Re: [swift-users] Anyone else having trouble getting swift to build?

2017-03-05 Thread David Sweeris via swift-users
Yep. Do I need to uninstall 8.2, though? I hadn't thought to try that until just now. Sent from my iPhone > On Mar 5, 2017, at 15:10, Jacob Bandes-Storch wrote: > > Shot in the dark: are you using the latest Xcode beta? > >> On Sun, Mar 5, 2017 at 3:03 PM, David Sweeris

[swift-users] Anyone else having trouble getting swift to build?

2017-03-05 Thread David Sweeris via swift-users
In particular, the "utils/build-script -x” will fail with 84 errors on my system. As best as I can tell, they're all/mostly linker errors because the correct .dylib files aren't being created (not sure why there wouldn’t be errors from that, but I don’t see any)? Is there an option to not

Re: [swift-users] @swift-ci Response time

2017-03-05 Thread Michael Gottesman via swift-users
> On Mar 5, 2017, at 11:58 AM, Michael Gottesman wrote: > > >> On Mar 4, 2017, at 5:24 PM, Mohit Athwani via swift-users >> > wrote: >> >> Hello, >> >> I submitted my first pull request ever and I'm super excited! >>

Re: [swift-users] @swift-ci Response time

2017-03-05 Thread Michael Gottesman via swift-users
> On Mar 4, 2017, at 5:24 PM, Mohit Athwani via swift-users > wrote: > > Hello, > > I submitted my first pull request ever and I'm super excited! > > @swift-ci has been tagged to test my code and I'm wondering how long does it > take to perform it's tests and give me

Re: [swift-users] Proper Way to make Errors in Swift 3

2017-03-05 Thread Ole Begemann via swift-users
Have you tried explicitly casting the value to NSError when you pass it to Objective-C? I think it should work then. let myError: MyError = ... myObjCFunc(myError as NSError) On 02/03/2017 17:29, Ronak via swift-users wrote: Hi everyone, It looks like I’m still having issues exposing

Re: [swift-users] Confusing Error localizedDescription output

2017-03-05 Thread Ole Begemann via swift-users
It's how protocols work in Swift. errorDescription is a protocol requirement of LocalizedError (that is, it's part of the protocol definition, not just added in an extension). Only protocol requirements are dynamically dispatched. Take a look at the implementation of