Hm. I'm not sure if the performance difference is a hard limitation because
of implementation decisions, or if it would be possible to make the current
implementation as fast as the closure-based implementation. I don't
understand enough about the codegen (and about possible optimizations) to
make
Oh, also: for AnyIterator it was a pretty clear performance gain (in my
testing). I haven't tested other erasers such as AnySequence, but even if
they're faster, they will have to store more closures (instead of a single
base pointer) and will thus have memory overhead...
On Mon, Sep 19, 2016 at 9
I noticed that both UnsafePointer and UnsafeMutablePointer have the identical
method
public func withMemoryRebound(to: T.Type, capacity count: Int, _
body: (UnsafeMutablePointer) throws -> Result) rethrows -> Result
so that rebinding an immutable pointer gives you a _mutable_ pointer. That
Paulo, yes, I know for Debian that it starts with
https://wiki.debian.org/DebianMentorsFaq, but I can't claim to have gone
through the process myself. My sense is that for Swift to be a first-class
citizen in the Debian or Ubuntu repos that someone at Apple should (not
must) sponsor it.
On Sun, S
Hello all,
(+cc Ted Kremenek, John Holdsworth, Philippe Hausler)
Following up on
https://github.com/apple/swift-corelibs-foundation/pull/622#issuecomment-247630142,
I'd like to discuss expanding the range of platforms that are tested by
@swift-ci.
Currently, @swift-ci is capable of "test macOS pl
Oops, forgot to actually CC people. My bad!
On Mon, Sep 19, 2016 at 8:02 AM, Brian Gesiak wrote:
> Hello all,
> (+cc Ted Kremenek, John Holdsworth, Philippe Hausler)
>
> Following up on https://github.com/apple/swift-corelibs-foundation/
> pull/622#issuecomment-247630142, I'd like to discuss exp
Swift Android builds successfully for me. Following all the preliminary
steps from https://github.com/apple/swift/blob/master/docs/Android.md, such
as building libicu, I can successfully build with the following command on
the master branch of apple/swift this morning:
utils/build-script -R \
In case anyone's interested in writing some Python, here's a task for
giving utils/update-checkout a --tag option:
https://bugs.swift.org/browse/SR-2695
- Brian
On Mon, Sep 19, 2016 at 9:01 AM, Brian Gesiak wrote:
> Swift Android builds successfully for me. Following all the preliminary
> step
I've been trying to build Swift for Linux with --installable-package
to build a swift-package.tar.gz that I can install to another Linux
machine.
When I extract my package on the other machine, and try either
compiling a simple print("hello world") program either with swiftc, or
doing this in the
So I did some superstition as William suggested and started removing
and changing a bunch of build flags. At some point, the message went
away, and when I put the flags back, the message didn't come back.
My original attempt should have been a completely clean checkout and
rebuild from scratch. (T
I temporarily hacked around the NSXMLNode.swift integer literal
overflow error I mentioned in the other thread to continue the build.
I hit a few more problems afterwards.
First, there was some kind of segmentation fault. It looks like swift
crashed trying to build libXCTest.so.
=
Hello all,
I have two copies of Xcode on my development machine:
/Applications/Xcode-7.3.1.app and /Applications/Xcode.app (which is Xcode
8.0).
I have `Xcode > Preferences... > Locations > Command Line Tools` set to
/Applications/Xcode-7.3.1.app, since I need Xcode 7.3.1 to build a
different pro
Are you building within a shared folder? We have heard reports of this
happening in such an environment, but we don't have a handle on the exact steps
to reproduce. Getting that information would be very useful.
- Daniel
> On Sep 19, 2016, at 6:53 AM, Eric Wing via swift-dev
> wrote:
>
> I'
> On Sep 19, 2016, at 8:24 AM, Brian Gesiak via swift-dev
> wrote:
>
> Hello all,
>
> I have two copies of Xcode on my development machine:
> /Applications/Xcode-7.3.1.app and /Applications/Xcode.app (which is Xcode
> 8.0).
>
> I have `Xcode > Preferences... > Locations > Command Line Tools
This has been randomly failing a lot and I can't reproduce locally, Should I
disable this test for now?
fatal error: 'try!' expression unexpectedly raised an error:
POSIX.ShellError.popen(["echo", "foo"], read error: Bad file descriptor (9)):
file
/home/buildnode/disk2/workspace/oss-swift-incr
I would appreciate it if you would do so = ).
This is I imagine blocking @swift-ci testing.
Michael
> On Sep 17, 2016, at 12:43 AM, Ankit Aggarwal via swift-dev
> wrote:
>
> This has been randomly failing a lot and I can't reproduce locally, Should I
> disable this test for now?
>
> fatal e
If we disable this please make sure we have a bug tracking fixing it. This
seems worth investigating soon.
- Daniel
> On Sep 19, 2016, at 9:27 AM, Michael Gottesman wrote:
>
> I would appreciate it if you would do so = ).
>
> This is I imagine blocking @swift-ci testing.
>
> Michael
>
>> O
Here is your TWISt-shout Newsletter for the week of 2016-09-12 to 2016-09-18
https://github.com/pepperdog/TWISt-shout/blob/master/2016/TWISt-shout-2016-09-19.md
Enjoy!
-Kenny
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailm
> On Sep 19, 2016, at 1:24 AM, Martin R via swift-dev
> wrote:
>
> I noticed that both UnsafePointer and UnsafeMutablePointer have the identical
> method
>
>public func withMemoryRebound(to: T.Type, capacity count: Int,
> _ body: (UnsafeMutablePointer) throws -> Result) rethrows -> Resul
On 9/19/16, Daniel Dunbar wrote:
> Are you building within a shared folder? We have heard reports of this
> happening in such an environment, but we don't have a handle on the exact
> steps to reproduce. Getting that information would be very useful.
>
Unfortunately no. I didn't use shared folder
on Mon Sep 19 2016, Eric Wing wrote:
> On 9/19/16, Daniel Dunbar wrote:
>> Are you building within a shared folder? We have heard reports of this
>> happening in such an environment, but we don't have a handle on the exact
>> steps to reproduce. Getting that information would be very useful.
>>
on Mon Sep 19 2016, Eric Wing wrote:
> I've been trying to build Swift for Linux with --installable-package
> to build a swift-package.tar.gz that I can install to another Linux
> machine.
>
> When I extract my package on the other machine, and try either
> compiling a simple print("hello world"
22 matches
Mail list logo
