Re: [swift-dev] prefix map ambiguous

it happens when the n is a literal let a:[Int] = [1, 2, 3] let f:(Int) -> Int = { $0 + 5 } print(a.prefix(5).map(f)) ab.swift:4:7: error: ambiguous use of 'prefix' print(a.prefix(5).map(f)) ^ Swift.Collection:85:17: note: found this candidate public func prefix(_ maxLength: Int) ->

Re: [swift-dev] State of String: Ergonomics, and You!

On Jan 10, 2018, at 11:55 AM, Michael Ilseman via swift-dev wrote: > ## String Ergonomics > > Ergonomics is an area that’s not been well-served by String. Collection > conformance and multi-line literals in Swift 4 were a welcome first step. > But, trying to write a

Re: [swift-dev] State of String: ABI & Performance

On Jan 11, 2018, at 12:32 PM, Michael Ilseman wrote: >>> We may also want a compact 5-bit encoding for formatted numbers, such as >>> 64-bit memory addresses in hex, `Int.max` in base-10, and `Double` in >>> base-10, which would require 18, 19, and 24 characters

Re: [swift-dev] State of String: ABI & Performance

> On Jan 11, 2018, at 17:34, Michael Ilseman wrote: > > > >> On Jan 11, 2018, at 4:20 PM, Ben Cohen > > wrote: >> >> >> >>> On Jan 11, 2018, at 12:32 PM, Michael Ilseman via swift-dev >>>

Re: [swift-dev] prefix map ambiguous

Hi Kelvin, Can you give a bit more detail on the type of the sequence, and which compiler version you’re seeing this on? I can’t reproduce this with a recent Xcode or a recent master toolchain with this code: let sequence = 0..<10 let n = 5 let f = { $0*2 } sequence.prefix(n).map(f) Thanks

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #1021

Sorry for the noise, I see that you'd already taken care of this with d104a7aec405177384a4cf92a101b99297183fed. vedant > On Jan 11, 2018, at 5:36 PM, Vedant Kumar wrote: > > Hi Slava, > > I think there might be a separate compilation breakage related to: IRGen: > Remove

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #1021

Hi Slava, I think there might be a separate compilation breakage related to: IRGen: Remove FieldAccess::NonConstantIndirect. /Users/buildnode/jenkins/workspace/oss-lldb-swift-master-llvm-swift5-transition-incremental-osx/lldb/source/Symbol/SwiftASTContext.cpp:6891:38: error: no member named

Re: [swift-dev] State of String: ABI & Performance

> On Jan 11, 2018, at 4:20 PM, Ben Cohen wrote: > > > >> On Jan 11, 2018, at 12:32 PM, Michael Ilseman via swift-dev >> > wrote: >> >> For a more general solution, I think a `var numericValue: Int? { get }` on >>

Re: [swift-dev] State of String: ABI & Performance

> On Jan 11, 2018, at 2:17 PM, Michael Ilseman via swift-dev > wrote: > > > >> On Jan 11, 2018, at 2:06 PM, Tony Allevato > > wrote: >> >> >> >> On Thu, Jan 11, 2018 at 12:32 PM Michael Ilseman via swift-dev

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #1021

Hi Doug, Slava, Looks like this is still an issue — just hit this on https://github.com/apple/swift/pull/13879 Does this failure look familiar to either of you? — Itai On 11 Jan 2018, at 7:12, swift-ci--- via swift-dev wrote: ## # [FAILURE] oss-swift-package-osx [#1021] Build URL: |

Re: [swift-dev] State of String: ABI & Performance

> On Jan 11, 2018, at 2:06 PM, Tony Allevato wrote: > > > > On Thu, Jan 11, 2018 at 12:32 PM Michael Ilseman via swift-dev > > wrote: > Hi Chris! > > +CC Michael Gottesman, as I veer into talking about ARC. > > >

Re: [swift-dev] State of String: ABI & Performance

On Thu, Jan 11, 2018 at 12:32 PM Michael Ilseman via swift-dev < swift-dev@swift.org> wrote: > Hi Chris! > > +CC Michael Gottesman, as I veer into talking about ARC. > > > On Jan 10, 2018, at 9:29 PM, Chris Lattner wrote: > > On Jan 10, 2018, at 11:55 AM, Michael Ilseman via

Re: [swift-dev] State of String: ABI, Performance, Ergonomics, and You!

> On Jan 11, 2018, at 8:53 AM, Omar Charif via swift-dev > wrote: > > Hi Michael, > > I have been doing some research on fast string matching algorithm that I > developed recently and I spent some time testing and benchmarking the > algorithm and it seems fine so far.

Re: [swift-dev] State of String: ABI & Performance

Hi Chris! +CC Michael Gottesman, as I veer into talking about ARC. > On Jan 10, 2018, at 9:29 PM, Chris Lattner wrote: > > On Jan 10, 2018, at 11:55 AM, Michael Ilseman via swift-dev > > wrote: >> (A gist-formatted version

Re: [swift-dev] [Swift CI] Build Still Failing: 1. OSS - Swift ASAN - OS X (master) #927

Fixed, this was due to new jobs added to CI. Thanks, Mishal Shah > On Jan 11, 2018, at 11:02 AM, Ben Langmuir wrote: > > Mishal, macOS-10 is out of space and all jobs failed. Could you take a look? > > >> On Jan 11, 2018, at 7:17 AM, Douglas Gregor

Re: [swift-dev] [Swift CI] Build Still Failing: 1. OSS - Swift ASAN - OS X (master) #927

Mishal, macOS-10 is out of space and all jobs failed. Could you take a look? > On Jan 11, 2018, at 7:17 AM, Douglas Gregor wrote: > > “No space left on device" > >> On Jan 11, 2018, at 6:36 AM, swift...@swift.org >> wrote: >> >> New issue

Re: [swift-dev] Default implementations from protocols and ABI stability

You’re “safe" here: in a library with resilience enabled, protocol extension methods are not emitted into the client unless they’re marked @inlinable (or however that ends up being spelled when we’re done with SE-0193). That said, you can’t be sure someone didn’t just implement their own

[swift-dev] Default implementations from protocols and ABI stability

Given the tentative ideas already being worked on for ABI stability what would be the place that code associated with a default implementation of a method on a protocol live? e.g. FooKit has some code that is similar to this: public struct SomeOptions : RawRepresentable { public

Re: [swift-dev] State of String: ABI, Performance, Ergonomics, and You!

Hi Michael, I have been doing some research on fast string matching algorithm that I developed recently and I spent some time testing and benchmarking the algorithm and it seems fine so far. It is slightly similar to the one I proposed to Swift 3 or 4 months ago, it is doing some processing

Re: [swift-lldb-dev] [swift-users] Discourse forum rollout next week!

:thumbsup: Charles > On Jan 10, 2018, at 2:22 PM, Nicole Jacque via swift-users > wrote: > > Hi All- > > First of all, a big thank you to everyone who has provided feedback on our > prototype Discourse forum. We are ready to move forward with the transition! > The

Re: [swift-lldb-dev] [swift-dev] Switching swift to C++14

Thanks Ben. My apologies for the slow follow up since I was out. I think we can continue to just conditionally enable C++14 for now for building swift in Windows until we figure out a better strategy. > On Jan 8, 2018, at 12:32 PM, Ben Langmuir wrote: > > Hi Ted, > >

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

Thanks Ben. My apologies for the slow follow up since I was out. I think we can continue to just conditionally enable C++14 for now for building swift in Windows until we figure out a better strategy. > On Jan 8, 2018, at 12:32 PM, Ben Langmuir wrote: > > Hi Ted, > >

Re: [swift-dev] [Swift CI] Build Still Failing: 1. OSS - Swift ASAN - OS X (master) #927

“No space left on device" > On Jan 11, 2018, at 6:36 AM, swift...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-incremental-ASAN-RA-osx [#927] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-ASAN-RA-osx/927/ >

[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #1021

Title: Report [FAILURE] oss-swift-package-osx [#1021] Build URL:https://ci.swift.org/job/oss-swift-package-osx/1021/ Project:oss-swift-package-osx Date of build:Thu, 11 Jan 2018 06:39:53 -0600 Build duration:2 hr 32 min Identified problems:Regression test failed: This

Re: [swift-dev] State of String: ABI & Performance

> On 11. Jan 2018, at 06:36, Chris Lattner via swift-dev > wrote: > > On Jan 10, 2018, at 11:55 AM, Michael Ilseman via swift-dev > > wrote: >> (A gist-formatted version of this email can be found at >>