[swift-users] Confused by this error message

I’m currently refactoring some code (Swift 3.?, latest XCode), and I ended up with the following: func spansTSON() -> TSON { var docs = self.spans.map() { $0.tson } for (span, doc) in zip(self.spans, docs) { if let datum =

Re: [swift-users] Confused by this error message

> On Jan 30, 2017, at 3:19 PM, Travis Griggs wrote: > > I’m currently refactoring some code (Swift 3.?, latest XCode), and I ended up > with the following: > > func spansTSON() -> TSON { > var docs = self.spans.map() { $0.tson } > for

Re: [swift-users] Importing Foundation or Glibc in REPL on Ubuntu 16.10 failing

Hmm... this sounds like this may be a good integration test. I am not sure what is going on here though. If I have a moment I will take a look a bit later today. Michael > On Jan 28, 2017, at 1:22 PM, Peter Ronnquist via swift-users > wrote: > > I have the same

[swift-users] Importing Foundation or Glibc in REPL on Ubuntu 16.10 failing

I have the same problem with importing Glibc into the REPL with "Swift 3.1 Development", Ubuntu 16.10, Jan 22, 2017, that was reported on the snapshot from 15 December (see below). Is this working for anyone? Best Regards Peter Ronnquist On Monday 19 December Chris Double wrote: Using

Re: [swift-users] Importing Foundation or Glibc in REPL on Ubuntu 16.10 failing

Peter, what are you doing specifically. I.e. are you passing any arguments to swift or something like that? Can you give a full reproducer? Also can you type swift -v to confirm the version #? Michael > On Jan 30, 2017, at 12:04 PM, Michael Gottesman via swift-users >

Re: [swift-users] Importing Foundation or Glibc in REPL on Ubuntu 16.10 failing

Interesting... it looks like we /do/ have an integration test that imports glibc into the repl: https://github.com/apple/swift-integration-tests/blob/master/repl/test-repl-glibc.py Probably could use one

Re: [swift-users] TWISt-shout Newsletter 2017-01-30

Hi All. Here is your TWISt-shout Newsletter for the week of 2017-01-23 to 2017-01-29 https://github.com/pepperdog/TWISt-shout/blob/master/2017/TWISt-shout-2017-01-30.md Enjoy! -Kenny

Re: [swift-users] @NSCopying semantic does not appear to copy in Swift initializer

Haha yes, you're right. I misunderstanded your idea, sorry. Indeed, in Obj-C, we have the freedom to decide on whether or not assign a value to a property by invoking setter or by accessing ivar directly and Apple's official documentation apparently suggested that we should always access the

Re: [swift-users] @NSCopying semantic does not appear to copy in Swift initializer

On 30 Jan 2017, at 10:12, Torin Kwok wrote: > In Obj-C, if a property has promised that it conforms to > porotocl and that it would respect copying semantic by being qualified > with `@property (copy)`, then we assign a value to `ivar` through the > setter by writting down

Re: [swift-users] @NSCopying semantic does not appear to copy in Swift initializer

On 27 Jan 2017, at 18:56, Jordan Rose via swift-users wrote: > @NSCopying currently does not affect initializers. … it's not 100%, for-sure > a bug. Just by way of context, this current behaviour closely matches Objective-C conventions, where `-init` methods directly

Re: [swift-users] SwiftPM package naming question

Feel free to send a sample package you're having issue with! On Mon, Jan 30, 2017 at 1:47 PM, David Sweeris via swift-users < swift-users@swift.org> wrote: > > On Jan 29, 2017, at 11:56 PM, Ankit Aggarwal > wrote: > > The package manager will pick name from manifest if