[swift-dev] Making the sign of NaNs unspecified to enable enum layout optimization

I had a discussion with Steve this morning about the potential for enum layout optimization with floating-point payloads. One great thing about floating-point is that it has NaNs, and lots of them. For the most part, the only significant semantic difference among these NaNs is whether they're

Re: [swift-dev] copy-on-write proposal

> On Oct 19, 2016, at 10:13 AM, Dave Abrahams via swift-dev > wrote: > > > on Tue Oct 18 2016, Erik Eckstein > wrote: > >>> On Oct 17, 2016, at 10:21 AM, Dave Abrahams wrote: >>> >>> >>> on Mon Oct 17 2016, Erik

Re: [swift-dev] PR Tests Failing

I just talked with Roman. He said that this was due to his commit earlier and that we need to do clean builds to work around it. Perhaps we should clean the workspaces? Michael > On Oct 19, 2016, at 2:39 PM, Michael Gottesman via swift-dev > wrote: > > My PR test is

[swift-dev] PR Tests Failing

My PR test is failing due to something unrelated: https://ci.swift.org/job/swift-PR-osx-smoke-test/2441/console Does anyone know what is going on? Michael ___ swift-dev mailing list swift-dev@swift.org

[swift-dev] imageView does't show the image with Swift 3 and Xcode 8

I recently migrated my app to Swift 3 and Xcode 8. The imageView didn't show the image if I re-open the app. I used viewWillAppear() for this function. The code is as below: let imageUrl: NSURL = NSURL(string: "\(userDefaults.string(forKey: "avatar_url")!)")! let imageData:NSData =

Re: [swift-dev] smoke test not very smoky?

Yes, I will fix it today by creating new preset for smoke test. Mishal Shah > On Oct 19, 2016, at 9:44 AM, Dave Abrahams via swift-dev > wrote: > > > on Wed Oct 19 2016, Dave Abrahams > wrote: > >> It still seems like, for a smoke test,

Re: [swift-dev] smoke test not very smoky?

on Wed Oct 19 2016, Jordan Rose wrote: >> On Oct 19, 2016, at 9:44, Dave Abrahams via swift-dev >> wrote: >> >> >> on Wed Oct 19 2016, Dave Abrahams > > wrote: >> >>> It still seems like, for a smoke test, we're doing way too much work.

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

One of the next builds succeeded, so the code is fine. The problem with just doing a clean build is the job might be available on several machines, but only the machine that gets it next will try a clean build—the other machines might not get the clean build command. > On Oct 19, 2016, at

Re: [swift-dev] smoke test not very smoky?

> On Oct 19, 2016, at 9:44, Dave Abrahams via swift-dev > wrote: > > > on Wed Oct 19 2016, Dave Abrahams > wrote: > >> It still seems like, for a smoke test, we're doing way too much work. >> This appears to be much more than what I get

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

Failing with: undefined symbol: _TTSgq5Vs5UInt8___TFs27_allocateUninitializedArrayurFBwTGSax_Bp_ more: + pushd /home/buildnode/disk1/workspace/oss-swift-incremental-RA-linux-ubuntu-16_10/swift-corelibs-foundation

Re: [swift-dev] smoke test not very smoky?

on Wed Oct 19 2016, Dave Abrahams wrote: > It still seems like, for a smoke test, we're doing way too much work. > This appears to be much more than what I get from build-script -t when > I run tests locally. Maybe I'm misunderstanding the intended role of > our smoke tests, but since nobody

Re: [swift-dev] smoke test not very smoky?

It still seems like, for a smoke test, we're doing way too much work. This appears to be much more than what I get from build-script -t when I run tests locally. Maybe I'm misunderstanding the intended role of our smoke tests, but since nobody is correcting me, I'm betting not. Anyway,