Re: [swift-dev] Path Swift

Hi, Piero. Sorry, I'm not quite sure what you're asking. Can you provide more details about the behavior you're seeing, and what you'd like it to do instead? Jordan > On Dec 7, 2015, at 5:06, Piero Sabino via swift-dev > wrote: > > Where I have to change the path of Swift? > Terminal or fold

Re: [swift-dev] Build error on OS X.

If you get the chance, please do file a bug at bugs.swift.org about this. Spaces in paths should not cause problems in 2015! Jordan > On Dec 7, 2015, at 17:01, Alexandros Salazar via swift-dev > wrote: > > Ah. Silly me. Thank you. > > On Mon, Dec 7, 2015 at 7:07 PM,

Re: [swift-dev] Starter project: Initializers for converting UnsafePointers to integers

The one I can think of is "sometimes a C API only lets you pass data as an Int (intptr_t) or as an UnsafeMutablePointer (void *), and you have the other kind of data". That said, it does seem to be sort of a niche use case. Jordan > On Dec 8, 2015, at 7:59, Michael Buckley via swift-dev > wro

Re: [swift-dev] Optionals in swift-clang

Hi, Seth. I think you're getting Clang / swift-clang mixed up with swiftc / swift. Clang is not the Swift compiler; the Swift compiler lives in the "swift" repo. Swift depends on Clang for its interoperation with C and Objective-C. A lot of the compiler encodes information about Optional, but mo

Re: [swift-dev] Beginner's questions about building Swift from source etc.

Looks like Mish Awadah has an answer on a later thread: > Here’s what I’ve done in the past to build a toolchain using the build > script. > > function build_osx_package() { > >YEAR=$(date +"%Y") >MONTH=$(date +"%m") >DAY=$(date +"%d") >TOOLCHAIN_VERSION="swift-SNAPSHOT-${YEAR}

Re: [swift-dev] Possibility to makes classes partial as C# language

Hi, Kévin. This sort of post is more appropriate for the swift-evolution list, and indeed there's already a bit of discussion around this. I suggest you look through the archives to see what you need to add. J

Re: [swift-dev] Beginner's questions about building Swift from source etc.

Ah! No, launch-with-toolchain's all that's supported. But it's an interesting direction to go. It'd be an Xcode feature more than a Swift feature, though, so bugs.swift.org isn't an appropriate place for the request. Glad everything's working manually now. Jordan > On Dec 10, 2015, at 22:09 ,

Re: [swift-dev] Initialization of default values

Members with initial values get their initialization synthesized into the body of the type's initializer. I think we do this during SILGen, i.e. when we go to emit a SIL body for the ConstructorDecl AST node. (We use the term "initial value" for "the thing on the right side of the equal sign fo

Re: [swift-dev] Building Foundation on FreeBSD

What's the compile command for the files that are failing? If the target triple there doesn't include a version number, it might be defaulting to something like "1.0". Jordan > On Dec 15, 2015, at 10:55 , Davide Italiano via swift-dev > wrote: > > Hi, > I'm in the process of porting Foundati

Re: [swift-dev] Building Foundation on FreeBSD

> On Dec 16, 2015, at 11:21 , Davide Italiano wrote: > > On Wed, Dec 16, 2015 at 11:17 AM, Jordan Rose wrote: >> What's the compile command for the files that are failing? If the target >> triple there doesn't include a version number, it might be defaulting to >> something like "1.0". >> >>

Re: [swift-dev] `withUnsafePointer` mutates `self`

> On Dec 16, 2015, at 0:12 , Dave Abrahams via swift-dev > wrote: > >> Yeah but we want to move in the direction of making that more reliable, not >> less. > > I am not sure I agree with you. I would defer to John McCall on this one, > but my understanding is that it's an explicit non-goal

Re: [swift-dev] inout and aliasing in the optimizer

> On Dec 17, 2015, at 14:48, Joe Groff via swift-dev > wrote: > >> >> On Dec 17, 2015, at 2:34 PM, Erik Eckstein via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Hi, >> >> I'm currently working on improving alias analysis in the optimizer and I run >> into following problem: >>

[swift-dev] StdlibUnittest and Debug compilers

Hi, all. I filed SR-292 today complaining about StdlibUnittest taking 13 minutes to build on my machine, 9 of which are spent in SIL optimization. I had a pretty strong feeling that this happened some time in the last few months. Continuing to experiment,

Re: [swift-dev] Optionals in swift-clang

Hi, Seth. Sorry for not getting back to you sooner! I don't think we have anything exactly like this, but there's sort of a sequence diagram in Chris and Joe's talk at the LLVM conference, "Swift's High-Level IR ". I'd say it looks something like this: 1. Parsing 2

Re: [swift-dev] metatype of Int

I think Jon's trying to build something on top of swiftc or SourceKit. Yes? You can do something like this to build your own metatype: ASTContext &ctx = … Type intTy = ctx.getIntDecl()->getDeclaredType(); auto *intMetaTy = MetatypeType::get(intTy, ctx); And then compare types using TypeBase::isE

Re: [swift-dev] Building Foundation on FreeBSD

> On Dec 19, 2015, at 7:14 , Davide Italiano wrote: > > On Fri, Dec 18, 2015 at 7:58 AM, Davide Italiano > wrote: >> On Wed, Dec 16, 2015 at 2:25 PM, Jordan Rose wrote: >>> On Dec 16, 2015, at 11:21 , Davide Italiano wrote: On Wed, Dec 16, 2015 a

Re: [swift-dev] [swift-corelibs-dev] Defining _GNU_SOURCE for module-map-included headers

Hm. If this is the right setting to set on everybody's system, we could add it as part of Clang initialization (for the Clang inside Swift). Otherwise, you can use "-Xcc" to pass extra flags to Clang, in this case "-Xcc -D_GNU_SOURCE=1". Hope that helps, Jordan > On Dec 20, 2015, at 2:29 , Dmi

Re: [swift-dev] [swift-corelibs-dev] Defining _GNU_SOURCE for module-map-included headers

> On Dec 21, 2015, at 10:57 , Pierre Habouzit wrote: > >> On Dec 21, 2015, at 9:34 AM, Jordan Rose via swift-corelibs-dev >> wrote: >> >> Hm. If this is the right setting to set on everybody's system, we could add >> it as part of Clang initialization (for the Clang inside Swift). Otherwise,

Re: [swift-dev] Building Foundation on FreeBSD

> On Dec 20, 2015, at 4:14 , Davide Italiano wrote: > > On Sun, Dec 20, 2015 at 5:07 AM, Davide Italiano > wrote: >> On Sat, Dec 19, 2015 at 11:28 PM, Jordan Rose wrote: >>> >>> On Dec 19, 2015, at 7:14 , Davide Italiano wrote: >>> >>> On Fri, Dec 18, 2015 at 7:58 AM, Davide Italiano >>>

Re: [swift-dev] Compiling on RHEL 7

My bad (and Kevin's bad). The test requires Objective-C, but we forgot to include that as a requirement. If you pull more recent changes the test should be disabled on non-Apple platforms. Jordan > On Dec 23, 2015, at 16:11, Jeremy Fergason via swift-dev > wrote: > > I have successfully buil

Re: [swift-dev] Linker script on Linux

> On Dec 30, 2015, at 17:49, Luke Howard via swift-dev > wrote: > > >> On 31 Dec 2015, at 12:33 PM, Joe Groff > > wrote: >> >> >>> On Dec 30, 2015, at 1:24 AM, Luke Howard via swift-dev >> > wrote: >>> >>> Per [SR-404], anything that cons

Re: [swift-dev] clang version requirements?

Hi, Tom. I wouldn't expect 3.7 or 3.8 to cause any problems when used as the compiler building Swift. You'll note that Swift embeds its own version of LLVM and Clang for later use; it will not (and cannot) use the standard one on your system. More information on that is available on the Swift we

Re: [swift-dev] SIL: "unowned" the calling convention and "unowned" the variable ownership convention

Hi, Michael. The calling convention is equivalent to the 'unowned(unsafe)' variant of 'unowned', so I don't think it's entirely unrelated. I don't like "Immediate" because I don't know what it means. Admittedly I don't work on SIL, but when is something passed "immediate" as opposed to "guarant

Re: [swift-dev] Testing fails in GYBUnicodeDataUtils.py

> On Jan 4, 2016, at 12:40, Tom Gall via swift-dev wrote: > > Building with: ./swift/utils/build-script -R -t --foundation > > on Linux (gentoo amd64) fails with > > + /usr/bin/cmake --build > /home/tgall/swift/build/Ninja-ReleaseAssert/swift-linux-x86_64 -- -j4 > SwiftUnitTests > > [6/29] Ge

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

Oops. Of course. Missed _runtime(objc). Jordan > On Mar 18, 2016, at 14:14 , no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#3530] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/3530/ >

Re: [swift-dev] Swift Playground

Hi, Tysun. I'm afraid playgrounds are still considered an Xcode feature, not part of the Swift open source project. Requesting support for watchOS should be filed as a Radar (bugreport.apple.com). Best, Jordan > On Mar 14, 2016, at 15:16 , Maclachlan Tysun via swift-dev > wrote: > > Good eve

Re: [swift-dev] Developing Swift in Xcode

> On Mar 14, 2016, at 14:05 , Ryan Lovelett via swift-dev > wrote: > > On Mon, Mar 14, 2016, at 04:54 PM, Ben Langmuir via swift-dev wrote: >> >>> On Mar 14, 2016, at 1:51 PM, Kenny Leung via swift-dev >>> wrote: >>> >>> Hi Ben. >>> >>> Argghh! >>> >>> Question: why generate Xcode project

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

Unrelated and harmless: this test is probabilistic. > On Mar 16, 2016, at 10:00 , no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#2761] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/2761/ >

Re: [swift-dev] Returning more than two scalars from C code

> On Mar 22, 2016, at 12:06, Bryan Chan via swift-dev > wrote: > > jgr...@apple.com wrote on 2016-03-22 02:37:47 PM: > > > The runtime functions are hacked in various unsavory ways to give > > them Swift-like calling conventions. Many of them also have > > important semantics that the compil

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

I think Doug just changed things in this area, so it's entirely possible. > On Mar 28, 2016, at 17:49, Michael Ilseman via swift-dev > wrote: > > I reverted to unblock the build. But, I have no idea why this would fail the > way it is. The error message "error: 'swift_name' attribute cannot be

Re: [swift-dev] Swift incremental compile profiling

Hi, Sam. I don't think we currently have a good answer for this built into xcodebuild or xctool, and it's a reasonable idea. (Ideally all builds would be fast enough that it wouldn't matter! That's obviously not where we are.) Since '-debug-time-function-bodies' is now public knowledge, I'll sha

Re: [swift-dev] Why are we re-linking?

I imagine it's because your git hash has changed, which is used in the --version output for swiftc. I'm not sure how to avoid that cost entirely, but we could add a CMake option to not do it (which you could set locally), and we could probably move it to a library that isn't used by most of thos

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

Hey, Saleem. How do you expect this to differ from normal symbol visibility? It seems to me that in a shared library, any public symbol is either exported or imported, depending on whether it has a definition, and any non-public symbol is default. (Unlike C, we expect to have sensible rules here

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

> On Apr 6, 2016, at 11:31, Saleem Abdulrasool wrote: > > On Wed, Apr 6, 2016 at 11:18 AM, Jordan Rose > wrote: > Hey, Saleem. How do you expect this to differ from normal symbol visibility? > It seems to me that in a shared library, any public symbol is either ex

Re: [swift-dev] Why are we re-linking?

> On Apr 7, 2016, at 14:01, Chris Lattner wrote: > > >> On Apr 6, 2016, at 11:08 AM, Jordan Rose via swift-dev >> wrote: >> >> I imagine it's because your git hash has changed, which is used in the >> --version output for swiftc. I'm not

Re: [swift-dev] repl/test-repl-glibc.py Failure on Ubuntu

+swift-lldb-dev > On Apr 14, 2016, at 7:20 , Joseph Bell via swift-dev > wrote: > > Ryan, thanks. I've voted on SR-1109 and will add the steps I use to > reproduce as well. > > I think now its clear why the 14.04 and 15.10 packaging tests are passing, > and that's because they aren't runn

Re: [swift-dev] Potential Bug in SE-0029 (Remove implicit tuple splat behavior from function applications)

Good catch. Seems like an issue with the diagnostic. Can you file a bug at bugs.swift.org? Jordan > On Apr 18, 2016, at 13:45, David Sweeris via swift-dev > wrote: > > I was updating some old code to Swift 2.2, and came across an unexpected > tuple splat warning. This code is all you need to

Re: [swift-dev] "does not conform to protocol" --> Tell me what to add

Xcode does tell you which members are not present; they're in the notes for the "does not conform" message, which you can see in the Issue Navigator or Log Navigator. I'm pretty sure we have an outstanding Radar about making fix-its for these too, but it's hard to know where in your type or exte

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

I'm confused as to why this wouldn't have failed the first time I ran the tests. Sorry, will fix promptly. Jordan > On Apr 21, 2016, at 11:10, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3545] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> I, personally, *really* don’t want yet another decorator keyword to indicate > the intent here, because I believe the user has already indicated intent by > stating conformance to the protocol P. I don't find this so compelling in a language with defaulted requirements. The place where we're

Re: [swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

> On Apr 29, 2016, at 23:46, Karl Wagner via swift-dev > wrote: > >> >> On 22 Apr 2016, at 06:46, Timothy Wood > > wrote: >> >> >>> On Apr 19, 2016, at 1:57 AM, Karl Wagner via swift-dev >> > wrote: >>> >>> I’m trying to cross-compile S

Re: [swift-dev] [swift-users] Swift Package Manager and main.swift

[+swift-dev, bcc swift-users] I’d be fine with supporting “Main.swift”. The one downside is that it could change behavior for existing projects relying on “Main.swift” being a library file, and that might mean it’s not worth making a change. Jordan > On May 1, 2016, at 23:34, Kostiantyn Koval

Re: [swift-dev] [swift-users] Swift Package Manager and main.swift

My concern is not about people who have both main.swift and Main.swift; it's people who have libraries/frameworks (no main.swift) where one of the source files happens to be named Main.swift. This isn't likely, but it is possible. We're certainly not going to drop "main.swift" in favor of "Main.

Re: [swift-dev] [swift-users] Swift Package Manager and main.swift

If it were just SwiftPM that would be fine, but I'd like someone to sign off on it being okay to (potentially) break existing Xcode projects as well. (This needs Xcode- and compiler-side changes as well, unfortunately. It's not just the package manager.) Jordan > On May 2, 2016, at 10:52, Max

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 15.10 - Long Test (master) #87

Dave, I think this really is you, even if it's something the compiler should accept. (I didn't look too closely.) Jordan > On May 2, 2016, at 12:47, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10-long-test [#87] > > Build URL: > h

Re: [swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

> On May 3, 2016, at 10:40, Karl Wagner via swift-dev > wrote: > > >> On 2 May 2016, at 18:42, Joseph Bell > > wrote: >> >> Karl, >> >> A number of us are on Slack working with ARM support - would you like an >> invite? >> >> Joe >> > > Hi, > > yes that would

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

> 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-dev >

Re: [swift-dev] Using locally built toolchain in Xcode

You don't actually need to sign the toolchain; it just needs an Info.plist. Dmitri, Mishal, is there any reason the build-toolchain script doesn't provide one? Jordan > On May 3, 2016, at 23:43, Rob Allen via swift-dev wrote: > > Hi, > > I've used swift/utils/build-toolchain to create a too

Re: [swift-dev] [Swift CI][OS X] Test failures

Looking into the driver failure. > On May 5, 2016, at 11:08, Mishal Shah via swift-dev > wrote: > > Two tests failing in master branch and its blocking from building toolchain. > > https://ci.swift.org/job/oss-swift-package-osx/ > > > First

Re: [swift-dev] [Swift CI][OS X] Test failures

Fixed in 8cfbf25. Jordan > On May 5, 2016, at 11:44, Jordan Rose wrote: > > Looking into the driver failure. > > >> On May 5, 2016, at 11:08, Mishal Shah via swift-dev > > wrote: >> >> Two tests failing in master branch and its blocking from building toolchain. >

Re: [swift-dev] Why are we re-linking?

lated directories: > > git log -1 --pretty=format:%H -- include/ lib/ tools/ > > I've wrote PoC code > > > 2016-04-12 2:22 GMT+09:00 Jordan Rose via swift-dev <mailto:swift-dev@swift.org>>: > >> On Apr 7, 2016, at 14:01, Chris Lattner > <mailto

Re: [swift-dev] Why are we re-linking?

> On May 6, 2016, at 09:23, Dmitri Gribenko wrote: > > On Fri, May 6, 2016 at 9:16 AM, Jordan Rose wrote: >> Hm. That might be a nice balance, and it’s not entirely a lie: that’s the >> version of the compiler that you’re using, if not the stdlib and runtime. >> I’d still like to put it behind

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1250

This is a configuration issue; Mishal and I will work it out. > On May 9, 2016, at 00:41, Daniel Dunbar via swift-dev > wrote: > > I can't tell what failed here: > > > YEAR:2016 > MONTH:05 > DAY:09 > TOOLCHAIN_VERSION:swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a > ARCHIVE_DIR:swift-DEVELOPMENT-SNA

Re: [swift-dev] How to run the tests out-of-tree?

Hi, Karl. I don’t think it would be too hard to handle most of them. The tests are actually pretty standalone: they require the LLVM tool “lit ” (in llvm/utils/lit/) and some helper tools from the build directory like “FileCheck” and “not”. To run the

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 10:44, Joe Groff wrote: > > >> On May 12, 2016, at 9:27 AM, Jordan Rose via swift-dev > <mailto:swift-dev@swift.org>> wrote: >> >> >> - I’m uncomfortable with using the term “undefined behavior” as if it’s >> universal

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

[+swift-corelibs-dev] I don't think Foundation even tries to do incremental builds. I wonder if XCTest.so needs to be marked as a dependency somewhere in the higher-level build system. Jordan > On May 12, 2016, at 15:52, Brian Croom wrote: > > I'm not sure where the resiliency work stands, bu

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 18:34, Andrew Trick wrote: > >> - On the flip side, I think we do need to preserve the ability to >> reference-cast in order to send Objective-C messages, at least for now. I >> don’t know how I want to expose that to users, though. (In general it’s >> probably worth see

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 18:56, Andrew Trick wrote: > >> - What was the thought behind putting UnsafeBytePointer in PointerTypeKind? >> OpaquePointer isn’t there, and I’m concerned about places that test if >> something’s a pointer by checking that the pointee type is non-null (by far >> the com

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (master) #4811

I think previous builds were blocked on earlier stages, so the actual change that caused this problem would have snuck in a while ago. Jordan > On May 19, 2016, at 16:34, Tony Parker via swift-dev > wrote: > > Huh, that’s odd. I can’t see how this diff would cause a change in the output > of

Re: [swift-dev] build-script -x freezing?

Hypotheses: - There are several executables that get linked around the same time (swiftc, swift-ide-test, sil-opt, etc), which leads to swapping. - Building the standard library with a debug compiler is really slow. - There’s actually a bug here somewhere, possibly due to a newer version of CMake

Re: [swift-dev] SwiftGlibc: Use VFS overlay instead of -fmodule-map-file

Hi, Rintaro. That’s a clever solution; it would mean we wouldn’t be blocked by talking to the Clang folks about making module map search paths SDKROOT-relative. That said, the VFS is a fairly, well, hacky piece of Clang, and I’m not sure we’d want to add a new dependency on it. Ben, Daniel, what

Re: [swift-dev] [swift-evolution] Possible bug with arithmetic optional comparison ?

I wouldn’t phrase it this way. “nil” could just as easily been above all of the integers. We added overloads for < and friends that took optionals so that you could sort an array by passing < and get something reasonable out without having to provide your own comparison function, but you’re not

[swift-dev] JIRA labels (no worries)

Hey, Brian. Re: your comment about labels : > By the way, I'm curious for your thoughts on the swift-3.0 label, which I > introduced in > https://lis

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

[+swift-build-dev] Doesn't look like any of these changes would have affected the package manager. Maybe the blamelist is missing something? /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Tests/Functional/MiscellaneousTests.swift:285: error: -[FunctionalTestSuite.Miscell

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

Ah, my bad, the next build passed cleanly. Jordan > On May 27, 2016, at 15:08, Jordan Rose wrote: > > [+swift-build-dev] Doesn't look like any of these changes would have affected > the package manager. Maybe the blamelist is missing something? > > /Users/buildnode/jenkins/workspace/oss-swift

Re: [swift-dev] Delaying the enforcement of ".self" out of Swift 3?

We have a bug for this, https://bugs.swift.org/browse/SR-899. I had pretty much the same reaction you did, which is that it's definitely a bug but it's probably not worth changing right now. Jordan > On Jun 2, 2016, at 13:21, Douglas Gregor via swift-dev > wrote: > > Hi all, > > While work

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (swift-3.0-preview-1) #532

This one isn't me. Daniel, any idea why this test could fail? Jordan > On Jun 3, 2016, at 10:09, no-re...@swift.org wrote: > > [FAILURE] oss-swift-3.0-preview-1-incremental-RA-linux-ubuntu-14_04 [#532] > > Build URL: > https://ci.swift.org/job/oss-swift-3.0-preview-1-incremental-RA-linux-ub

Re: [swift-dev] NSProxy dynamic casting to Swift or ObjC class behaves differently

> On Jun 8, 2016, at 10:52, Joe Groff via swift-dev wrote: > >> >> On Jun 8, 2016, at 12:44 AM, Yavuz Nuzumlalı via swift-dev >> wrote: >> >> Hi all, >> >> swift_dynamicCastClassUnconditional and >> swift_dynamicCastObjCClassUnconditional methods behave differently while >> verifying cast

Re: [swift-dev] Problem in parsing SIL

> On Jun 21, 2016, at 14:10, Joe Groff via swift-dev > wrote: > > >> On Jun 21, 2016, at 2:03 PM, Slava Pestov via swift-dev >> wrote: >> >> Hi Mikio, >> >> Try this: >> >> swiftc -frontend -emit-silgen classdecl.swift > classdecl.sil >> swiftc -parse-sil classdecl.sil >> >> I'm not sure

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

This isn’t me. SwiftPM folks, is this real? /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/Basic/PathPerfTests.swift:23: error: PathPerfTests.testJoinPerf_X10 : failed: The relative standard deviation of the measurements is 12.993% which is higher

Re: [swift-dev] Swift 3 on Linux

I’m afraid not. Only Xcode is supported for developing for iOS. Whether or not the Linux distribution of Swift supports cross-compilation to iOS, it still doesn’t include the SDKs or any of the tools for actually getting the app onto an iOS device. Best, Jordan > On Jun 22, 2016, at 23:18, Fa

Re: [swift-dev] [swift-users] Swift 3.0 Preview 1 Branch and Tag Updated

> On Jun 30, 2016, at 00:33, Drew Crawford via swift-users > wrote: > > Hi, > > I attempted to compile this on OSX El Capitan using the same process I've > been using for snapshots, and got very many failures. Can't find anything > related in bugreporter, mailing list, or google. > > Is th

Re: [swift-dev] Unmanaged API flip flop

> On Jul 4, 2016, at 13:32, Kyle Jessup via swift-dev > wrote: > > I have this code which uses Unmanaged and the API seems to vary depending on > if I am using a 3.0 Preview or a development snapshot. I see it now when > trying the June 13th/27th preview vs June 20th snapshot. > > class MyCl

Re: [swift-dev] Fixit for trailing closures

> On Jul 5, 2016, at 17:19, Ben Langmuir via swift-dev > wrote: > >> >> On Jul 5, 2016, at 4:34 PM, Xi Ge via swift-dev > > wrote: >> >> Hi Swift-devs, >> I have tried to add a fixit to help developers using trailing closures more, >> motivated by my observation d

Re: [swift-dev] Fixit for trailing closures

> On Jul 5, 2016, at 21:29, Xi Ge wrote: > >> >> On Jul 5, 2016, at 8:31 PM, Jordan Rose > > wrote: >> >>> >>> On Jul 5, 2016, at 17:19, Ben Langmuir via swift-dev >> > wrote: >>> On Jul 5, 2016, at 4:34 PM, Xi Ge via swift

Re: [swift-dev] Handling Windows C library Matrix

For anyone watching this thread, Saleem broke it down a little further for me in https://github.com/apple/swift/pull/3326. For now we decided to just add an autolink flag to the frontend (not the driver) to make sure we don't get the "wrong" C library by accident. We'll need to discuss further h

Re: [swift-dev] Fixit for trailing closures

> On Jul 6, 2016, at 10:31, Xi Ge wrote: > > > > > >> On Jul 6, 2016, at 9:39 AM, Jordan Rose > > wrote: >> >>> >>> On Jul 5, 2016, at 21:29, Xi Ge mailto:xi...@apple.com>> >>> wrote: >>> On Jul 5, 2016, at 8:31 PM, Jordan Rose >>>

Re: [swift-dev] [RFC] Finer grained OS checks

Thanks for sending this out, Saleem! I’m not convinced that gnu/uclibc/musl are environment variants worth testing for, nor do I think we actually want to model Android as a kind of Linux. It’s unclear whether “environment” is another set of mutually-exclusive options (enum-like) or a way to ch

Re: [swift-dev] id-as-Any and ObjC generic parameters

> On Jul 7, 2016, at 17:26, John McCall via swift-dev > wrote: > > Suppose we are calling a function that is generic over T, where T: AnyObject. > This comes up when e.g. calling an initializer for an ObjC generic class. > > Today we allow conversions from [String] to [NSString], String to N

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

It’s possible we’re not treating “macos” the same as “macosx”, and thus changing the way that methods with the same basename get imported. So it probably is that change. …yep, it looks like we look for literal platform name strings in ClangImporter.cpp and ImportDecl.cpp. Jordan > On Jul 12,

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

We’ll need it on the 2.3 branch too. Jordan > On Jul 12, 2016, at 13:05, Mishal Shah via swift-dev > wrote: > > We are also seeing these failures in swift-3.0-preview-3-branch, can we pull > this in to swift-3.0-preview-3-branch? > > https://ci.swift.org/view/swift-3.0-preview-3/job/oss-swif

Re: [swift-dev] Turns out Incremental builds were not actually incremental

IIRC this was deliberate because of some past issues with things not getting rebuilt. In particular, even an incremental build should trash the module cache folder every build, and I don’t think we do this. Nicole, do you remember specifically why this was changed? (Or Mishal, when back from vac

Re: [swift-dev] Turns out Incremental builds were not actually incremental

> On Jul 21, 2016, at 15:06, Michael Gottesman wrote: > > >> On Jul 21, 2016, at 2:54 PM, Jordan Rose wrote: >> >> IIRC this was deliberate because of some past issues with things not getting >> rebuilt. In particular, even an incremental build should trash the module >> cache folder every

[swift-dev] PR testing failing on test/IDE/print_omit_needless_words.swift

Hey, Max, any idea why my PR test keeps failing on this? I saw you update both the apinotes and the test, and other PR tests seem to be passing. https://ci.swift.org/job/swift-PR-osx/2678/testReport/Swift(iphonesimulator-i386)/IDE/print_omit_needless_words_swift/ Jordan _

Re: [swift-dev] End of source-breaking changes for Swift 3

Associating some proposals with their current implementers for the record… > On Jul 27, 2016, at 12:38, Ted Kremenek via swift-dev > wrote: > > Dear friends, > > Today is July 27 — and the last planned day to take source-breaking changes > for Swift 3. It has been an incredible ride to this p

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

Error copying directory from "/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/buildbot_incremental/swift-macosx-x86_64/lib/swift/appletvos" to "/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/buildbot_incremental/swift-macosx-x86_64/benchmark/lib/swift/appletvos”.

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

[+Doug] I’ve seen this come up a few times too. Clearing the module cache sometimes makes it go away, which seems really suspicious. I think we must have nondeterminism somewhere in error importing. Jordan > On Jul 29, 2016, at 02:56, Andrew Trick via swift-dev > wrote: > > I must be buildin

Re: [swift-dev] dispatch_block_t is imported wrong, breaks barrier blocks (SR-2246)

I’d suggest putting this over on swift-corelibs-dev, since it’s a Dispatch-specific issue. Jordan > On Aug 1, 2016, at 17:25, Kevin Ballard via swift-dev > wrote: > > For anyone following along, I've submitted a PR to fix this as > https://github.com/apple/swift/pull/3923. > > -Kevin > >

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

/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/foundation-linux-x86_64/TestFoundation/TestFoundation: symbol lookup error: /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/foundation-linux-x86_64

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

> On Aug 1, 2016, at 19:38, Jordan Rose wrote: > > /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/foundation-linux-x86_64/TestFoundation/TestFoundation: > symbol lookup error: > /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux

[swift-dev] Failure in optimized tests

I think this might be a real issue. Dave, what do you think? https://ci.swift.org/job/oss-swift_tools-RA_stdlib-RD_test-simulator/1863/consoleFull#-1050474920fca400bf-2f4a-462e-b517-e058d770b2d7 Every “Minimal.*Collection” suite is failing on this test: FAIL: ["MinimalRangeReplaceableRandomAcce

Re: [swift-dev] Is developer snapshot 2016-07-29 broken?

> On Aug 3, 2016, at 07:59, Erica Sadun via swift-dev > wrote: > > >> On Aug 1, 2016, at 5:11 PM, Joe Groff via swift-dev > > wrote: >> >>> >>> On Jul 31, 2016, at 5:12 AM, Charles Lane via swift-dev >>> mailto:swift-dev@swift.org>> wrote: >>> >>> I get a segmen

Re: [swift-dev] Is developer snapshot 2016-07-29 broken?

> On Aug 3, 2016, at 11:23, Jens Persson wrote: > > I've also tried the latest nightly (2 aug *), and I can verify that it's > broken in the same way as the latest dev snapshots. > (* https://swiftnightly.com , > swift-DEVELOPMENT-SNAPSHOT-2016-08-02-a.xctoolchain) >

Re: [swift-dev] Is developer snapshot 2016-07-29 broken?

have noticed that at least the three > latest dev snapshots (without symbols) are broken (ans the ones without > symbols don't include UnsafeRawPointer). > > I'd like to try out the new UnsafeRawPointer API, and it's currently not > possible (beta 4 doesn't in

Re: [swift-dev] linux long tests failing due to JUnit issue?

> On Aug 6, 2016, at 15:15, Dave Abrahams via swift-dev > wrote: > > > I don't really understand why JUnit would be relevant here, but we're > getting this failure after everything else seems to pass. > > [xUnit] [INFO] - Processing JUnit > [xUnit] [INFO] - [JUnit] - No test report file(s) we

Re: [swift-dev] Build failure on s390x

Hi, Vivian. RuntimeStubs.h (along with the rest of SwiftShims) is a header that gets shipped with the Swift library, so it can’t refer to anything outside of its folder. Since we don’t yet have a good way to annotate things as using the Swift calling convention in the SwiftShims headers, we shou

[swift-dev] Timeouts on Linux bots?

Hey, all. Any idea why the Linux bots would be timing out? (including my pull request testing ). I can see builds possibly taking longer than 30 minutes, but I wouldn’t expect the tests to do so, particularly not without the "long tests” enabled. J

Re: [swift-dev] Timeouts on Linux bots?

Hm. That’s a very slow test, but not 30 minutes slow. And it’s my test. I guess I should take a look. > On Aug 10, 2016, at 11:01, Mishal Shah wrote: > > Hi Jordan, > > The job is configured to timeout if it does not show any activity on the > console. In the PR build, we are seeing last tes

Re: [swift-dev] MemoryError in SIL/parse_stdlib_X.sil tests when building toolchain on Ubuntu 15.10

I think this is the spew of deprecation warnings thing I was investigating yesterday. I just merged the fix for that, so try updating to the latest master and try again. Jordan > On Aug 11, 2016, at 10:21, Mishal Shah via swift-dev > wrote: > > Hi, > > Can you please file a bug on bugs.sw

Re: [swift-dev] undefined symbol: _TFC10Foundation8NSNumberg25customPlaygroundQuickLookOs19PlaygroundQuickLook

+Foundation-Michael (and Tony). One more test to update? Problem with clean builds? Jordan > On Aug 11, 2016, at 16:15, Daniel Dunbar via swift-dev > wrote: > > Is anyone investigating this failure on the CI bots: > -- > /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu

  1   2   3   >