[swift-dev] The Swift Programming Language - GERMAN

Hey guys, this morning I read in a newsletter by NatashaTheRobot on Chris Lattner’s tweet about translating the Swift documentation. Thought that would be a nice idea to finally contribute to Swift, so I started immediately with the German version: https://github.com/DominicFrei/the-swift-progr

[swift-dev] bugs.swift.org usage

Now that I’ve published a tarball of the ARM swift compiler, I’m getting some messages about this or that not working. I’m curious about the intended usage/audience of bugs.apple.com . Should I encourage people to file bug reports, or do you only want bugs relating to t

Re: [swift-dev] [swift-users] Cross Compiling Swift for Bare Metal?

> On Dec 20, 2015, at 12:22 AM, Dmitri Gribenko via swift-users > wrote: > > Regarding the microcontroller that you referenced, I think it would be an > overly ambitious goal to try to make everything work with 256 Kb of flash and > 32 Kb of RAM. I would recommend to start with a more powerf

[swift-dev] Compiler crash - relates to protocol and protocol extension

Hi, I found a piece of code that could made the compiler crash, It’s can reproduce on Xcode 7.2(7C68) with Apple Swift version 2.1.1 (swiftlang-700.1.101.15 clang-700.1.81) Target: x86_64-apple-darwin15.2.0 the code is simply like: protocol FooType {   func bar(b: Int) } extension FooType {  

Re: [swift-dev] Compiler crash - relates to protocol and protocol extension

On Sun, Dec 20, 2015 at 4:42 AM, Jasl via swift-dev wrote: > Hi, > > I found a piece of code that could made the compiler crash, It’s can > reproduce on Xcode 7.2(7C68) with Apple Swift version 2.1.1 > (swiftlang-700.1.101.15 clang-700.1.81) Target: x86_64-apple-darwin15.2.0 > > the code is simpl

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] Dockerized Swift, Build Times and Other Notes Regarding CI

Hi Tom, > With docker compose, the following commands: > >> docker build -t swift-dev-image . >> docker create -it --name development -v >> /my/absolute/path/to/swift:/container/mount-point swift-dev-image >> docker start -ai development > > Become: > >> docker-compose up Fair enough (for som

Re: [swift-dev] metatype of Int

Yes, context.getIntDecl() was exactly what I was looking for. Thank you Jordan! On 12/18/2015 08:49 PM, Jordan Rose wrote: 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.g

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

> 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, > you can use "-Xcc" to pass extra flags to Clang, in this ca

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] [swift-corelibs-dev] Defining _GNU_SOURCE for module-map-included headers

> On Dec 21, 2015, at 11:00 AM, Jordan Rose wrote: > > >> On Dec 21, 2015, at 10:57 , Pierre Habouzit > > wrote: >> >>> On Dec 21, 2015, at 9:34 AM, Jordan Rose via swift-corelibs-dev >>> mailto:swift-corelibs-...@swift.org>> wrote: >>> >>> Hm. If this is the right

[swift-dev] FYI: Apple holiday shutdown

Hi Everyone, Just a head’s up that Apple has a holiday shutdown from Dec 24 to Jan 3 (and many people are already out). The web site, mailing lists and all other services should still be up, but don’t be surprised if there are additional delays in responding to threads and pull requests during

Re: [swift-dev] bugs.swift.org usage

> On Dec 21, 2015, at 8:31 AM, William Dillon via swift-dev > wrote: > > Now that I’ve published a tarball of the ARM swift compiler, I’m getting some > messages about this or that not working. I’m curious about the intended > usage/audience of bugs.apple.com . Shoul

Re: [swift-dev] [swift-users] Cross Compiling Swift for Bare Metal?

> On Dec 20, 2015, at 3:03 PM, William Dillon via swift-users > wrote: > > Though it might sound a little silly (because why not run linux), but > starting with a beagle bone black would not be a terrible way to begin with > bare metal work. It has plenty of RAM, you know that LLVM writes go

Re: [swift-dev] bugs.swift.org usage

> On Dec 21, 2015, at 11:17 AM, Chris Lattner via swift-dev > wrote: > > >> On Dec 21, 2015, at 8:31 AM, William Dillon via swift-dev >> wrote: >> >> Now that I’ve published a tarball of the ARM swift compiler, I’m getting >> some messages about this or that not working. I’m curious abou

Re: [swift-dev] [swift-users] Cross Compiling Swift for Bare Metal?

> On Dec 19, 2015, at 6:53 PM, Chaitanya Mannem via swift-users > wrote: > > Hi, > > > I wanted to know if it is possible to compile swift code for bare metal. I > know there is a runtime but does swift depend on it to execute even if I > don't use those features?, can I disable them someho

Re: [swift-dev] Reducing the size of Swift binaries by shortening symbols

> On Dec 20, 2015, at 9:53 PM, Dmitri Gribenko via swift-dev > wrote: > >> >> nm -a libswiftCore.dylib > strings.txt >> >> I also have a concern about making mangled names completely unreadable. >> Today, I can frequently at least get a gist of what the referenced entity is >> without a deman

Re: [swift-dev] Including third-party code in repo

On Dec 19, 2015, at 12:26 PM, Zhuowei Z via swift-dev wrote: > I'm currently working on a port of Swift to Android. Great! > Since Android's libc is missing a few required methods, I added code from a > few other sources to implement the functionality. Specifically, I added an > implementatio

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

[swift-dev] SwiftAndroid: Statically linking libicu and/or the stdlib?

Hi, I’m still working on the deployment and JNI side of SwiftAndroid (github.com/SwiftAndroid). After success with some basic tests I’ve started fleshing out a “Swifty” JNI interface and connected to some existing Swift library code I want to try out. Now I’m stuck and I hope someone with more

Re: [swift-dev] SwiftAndroid: Statically linking libicu and/or the stdlib?

On Mon, Dec 21, 2015 at 6:13 PM, Geordie Jay via swift-dev < swift-dev@swift.org> wrote: > ./utils/build-script -R --no-assertions -b -p --extra-swift-args > build-swift-static-stdlib=1 > This option builds static archives of the standard library, not a standard library that links in everythi