Re: [swift-dev] Cross-compiling (nearly) everything for RPi from OSX

> On 10 May 2016, at 04:11, Karl Wagner wrote: > > I’ve managed to cross-compile the swift tools for the Raspberry Pi from OSX. > > I thought I’d share my changes. Branch is here: > https://github.com/karwa/swift . I’ll work on > merging it soon. > > The only

Re: [swift-dev] swift (ABI) and Windows

On Tue, May 3, 2016 at 6:34 PM, Jordan Rose wrote: > > On Apr 26, 2016, at 08:43, Saleem Abdulrasool > wrote: > > On Tue, Apr 12, 2016 at 9:32 AM, Saleem Abdulrasool > wrote: > >> On Monday, April 11, 2016, Joe Groff wrote: >> >>> >>> > On Apr 11, 2016, at 3:19 PM, Saleem Abdulrasool via swift

Re: [swift-dev] Broken development snapshot

Hi Mikio, This issue has been resolved, please re-download the symbols pkg. https://bugs.swift.org/browse/SR-1460 Thanks, Mishal Shah > On May 10, 2016, at 9:07 PM, Mikio Takeuchi via swift-dev > wrote: > > It looks like the current (May 9) snapshot of master for Xcode with symbols > is br

Re: [swift-dev] LazyFilterCollection is not a Collection

On Mon, May 9, 2016 at 4:16 PM, Dmitri Gribenko wrote: > On Mon, May 9, 2016 at 11:46 AM, Rob Napier wrote: > > It violates the performance requirements. > > CollectionType.count requires O(1) access if Index is a > > RandomAccessIndexType. > > Hi Rob, > > We don't have RandomAccessIndexType any

[swift-dev] What do to when stdlib guidelines conflict with proposal?

I’m implementing SE-0017 but based on the standard library guidelines I think Unmanaged should have initializers that take UnsafePointer/UnsafeMutablePointer and vice-versa which would fit more naturally with the way other conversions work. A later commit already moved toOpaque to be an initia

Re: [swift-dev] LazyFilterCollection is not a Collection

Naively (and thinking about how this works on other platforms), I would expect Array(lazyFilterSequence) to iterate only once and take the hit of reallocation. Russ > On May 11, 2016, at 2:46 PM, Rob Napier via swift-dev > wrote: > > > On Mon, May 9, 2016 at 4:16 PM, Dmitri Gribenko

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3999

John, this is yours, right? > On May 11, 2016, at 3:38 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3999] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3999/ > > Project: o

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3999

> On May 11, 2016, at 3:40 PM, Bob Wilson wrote: > John, this is yours, right? Yeah, I'll take a look. John. > >> On May 11, 2016, at 3:38 PM, no-re...@swift.org >> wrote: >> >> [FAILURE] oss-swift-incremental-RA-osx [#3999] >> >> Build URL: https://ci.swift.or

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

+1 from the proposal author, although since it went through community review that doesn't make me an authority ;) On Wed, May 11, 2016 at 2:53 PM Russ Bishop via swift-dev < swift-dev@swift.org> wrote: > I’m implementing SE-0017 but based on the standard library guidelines I > think Unmanaged shou

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

On Wed, May 11, 2016 at 2:53 PM, Russ Bishop via swift-dev wrote: > I’m implementing SE-0017 but based on the standard library guidelines I think > Unmanaged should have initializers that take > UnsafePointer/UnsafeMutablePointer and vice-versa which would fit more > naturally with the way othe

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

> On May 11, 2016, at 4:50 PM, Dmitri Gribenko wrote: > > On Wed, May 11, 2016 at 2:53 PM, Russ Bishop via swift-dev > wrote: >> I’m implementing SE-0017 but based on the standard library guidelines I >> think Unmanaged should have initializers that take >> UnsafePointer/UnsafeMutablePointer

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

On May 11, 2016, at 8:17 PM, Russ Bishop via swift-dev wrote: > >> On May 11, 2016, at 4:50 PM, Dmitri Gribenko wrote: >> >> On Wed, May 11, 2016 at 2:53 PM, Russ Bishop via swift-dev >> wrote: >>> I’m implementing SE-0017 but based on the standard library guidelines I >>> think Unmanaged sh

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

> On May 11, 2016, at 10:18 PM, Chris Lattner wrote: > As Dmitri, we specifically discussed this in the core team meeting (I brought > it up :-). The problem is that we really only want the toOpaque() method to > exist on UnsafePointer and don’t have the ability to model that in the > languag

Re: [swift-dev] swift (ABI) and Windows

I merged Saleem's recent #2080 in my repo, and tested the same. Now I could build the libswiftCore.dll which can be used for Hello.swift. No _TMSS errors were occurred. > Unfortunately, ATM, the runtime is compacted into the stdlib, which has the small problem of making the stdlib have references