Re: [swift-dev] Transition to the Swift Forums -- mailing lists going into suspend mode

Whoops, that’s swift-infrastruct...@swift.org . > On Jan 17, 2018, at 6:07 PM, Nicole Jacque wrote: > > Hi All- > > We’re about to start the transition to our new Swift forums and I’ll be > setting the mailing lists to suspend mode

Re: [swift-lldb-dev] Transition to the Swift Forums -- mailing lists going into suspend mode

Whoops, that’s swift-infrastruct...@swift.org . > On Jan 17, 2018, at 6:07 PM, Nicole Jacque wrote: > > Hi All- > > We’re about to start the transition to our new Swift forums and I’ll be > setting the mailing lists to suspend mode

Re: [swift-corelibs-dev] Transition to the Swift Forums -- mailing lists going into suspend mode

Whoops, that’s swift-infrastruct...@swift.org . > On Jan 17, 2018, at 6:07 PM, Nicole Jacque wrote: > > Hi All- > > We’re about to start the transition to our new Swift forums and I’ll be > setting the mailing lists to suspend mode

[swift-dev] Transition to the Swift Forums -- mailing lists going into suspend mode

Hi All- We’re about to start the transition to our new Swift forums and I’ll be setting the mailing lists to suspend mode shortly so we can export/import the mailing list data. When the forums are open for business (ETA: sometime on Friday) I’ll update the swift.org website and send out one

[swift-corelibs-dev] Transition to the Swift Forums -- mailing lists going into suspend mode

Hi All- We’re about to start the transition to our new Swift forums and I’ll be setting the mailing lists to suspend mode shortly so we can export/import the mailing list data. When the forums are open for business (ETA: sometime on Friday) I’ll update the swift.org website and send out one

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - LLDB Incremental - OS X (master-llvm-swift5-transition) #61

Thanks! ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - LLDB Incremental - OS X (master-llvm-swift5-transition) #61

This didn't send to the list because the quoted section of the email was too long. Once again; I cherry-picked Slava's fix for the failures listed here: a5243443d (HEAD -> llvm-swift5-transition, origin/llvm-swift5-transition) Merge pull request #275 from

[swift-dev] [Call for testing] Catching debug info violations at -Onone

Hi, I would like to discuss the path towards enabling a new debug info verifier pass by default. This should improve the debug experience of users at `-Onone`. ## Problem Description Mandatory passes which run at `-Onone` can attach a wrong scope when they create instructions. This may result

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 (master) #2618

Test Case 'RepositoryManagerTests.testBasics' started at 2018-01-17 22:36:16.208 <>/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_04/swiftpm/Tests/SourceControlTests/RepositoryManagerTests.swift:199: error: RepositoryManagerTests.testBasics : Asynchronous wait failed

Re: [swift-dev] String comparison improvements

Hi Lance (and Michael — I’ll keep the conversation in one thread), Sounds reasonable. My one concern is that behavior around implicitly bridged strings is going to change, in a potentially problematic and "magic" way: ```swift let s1: String = … let s2: String = … let mySet = NSMutableSet()

Re: [swift-dev] String comparison improvements

> On Jan 17, 2018, at 1:46 PM, Itai Ferber via swift-dev > wrote: > > Hi Lance, > > I read Michael’s emails but I don’t remember at the moment — what is the new > string comparison implementation going to be based on? > It is the lexicographical ordering of

Re: [swift-dev] Testing, validation, and many-core machines

> On Jan 17, 2018, at 16:06, Michael Gottesman wrote: > > > >> On Jan 17, 2018, at 8:23 AM, David Zarzycki via swift-dev >> wrote: >> >> Hello, >> >> In docs/Testing.md, “long test” is acknowledged but never defined. When >> should tests be

Re: [swift-dev] String comparison improvements

Comments inline below > On Jan 17, 2018, at 1:46 PM, Itai Ferber wrote: > > Hi Lance, > > I read Michael’s emails but I don’t remember at the moment — what is the new > string comparison implementation going to be based on? > The new approach uses the lexicographical

Re: [swift-dev] String comparison improvements

Hi Lance, I read Michael’s emails but I don’t remember at the moment — what is the new string comparison implementation going to be based on? Also, how will this affect bridged strings? If I compare two `NSString`s, I may get a different result than if I compare the same two strings as

[swift-dev] String comparison improvements

Hey Swift-Dev, The swift standard library team have been working on a new implementation for comparing Swift strings for Swift 5. Michael touched on the motivations in the State of String email but I’ll summarize here: The Swift String comparison implementations on Apple platforms and Linux

Re: [swift-dev] Testing, validation, and many-core machines

> On Jan 17, 2018, at 8:23 AM, David Zarzycki via swift-dev > wrote: > > Hello, > > In docs/Testing.md, “long test” is acknowledged but never defined. When > should tests be marked “long_test”? I’m asking because there are arguably a > number of latent long_test tests

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

(Replying out-of-order) > Sadly, I don’t. I’m only an opinionated hobbyist in this domain, one who has > coded a lot of string processing over the years and understands at least some > of the tradeoffs. Wouldn’t it be amazing to be able to write a high performance lexer with all the

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

> On Jan 13, 2018, at 10:30 AM, Michael Ilseman via swift-dev > wrote: >> I wouldn’t overly rely on it for guidance on these issues give that it it >> stuck so squarely in the realm of UTF16. >> > > Wading a little into the weeds here, CharacterSet’s builtins model older

Re: [swift-dev] Protocol Devirtualizer Pass

I created a pull request for the protocol devirtualizer and the peephole optimizer at https://github.com/apple/swift/pull/13991. Really appreciate all the help from Arnold and Slava. Here is an example of what the transformation achieves (in conjunction with other existing passes of swift) :

Re: [swift-dev] Suggestions for open projects (GSoC 2018)

Hi Everyone, If you have an idea or are interested in mentoring, send it in now! Thanks, Anna > On Jan 8, 2018, at 5:17 PM, Anna Zaks wrote: > > Dear Swift Developers, > > The Swift project is applying to participate in Google Summer of Code 2018. > During GSoC, students

[swift-dev] Testing, validation, and many-core machines

Hello, In docs/Testing.md, “long test” is acknowledged but never defined. When should tests be marked “long_test”? I’m asking because there are arguably a number of latent long_test tests that are exposed on many-core machines. Speaking of many-core machines, there really isn’t a practical