What is the "correct" way to remove a Swift Dev snapshot from OS X? It
comes with a nice installer package it install is there an equivalent
for removal?
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
Thanks for your reply Dmitri. I ended up getting this working by manually
changing the SONAME and other internal references from within and to ICU
from the stdlib and APKs are now working on all the non-rooted devices I
have available to me.
I don't know my way around CMake to make major (or evide
I'm beginning to try to port some of my existing C code over to Swift
(you have no idea how excited that makes me). Unfortunately, I've hit a
stumbling block.
When interacting with some of the system/hardware interfaces in Linux it
sometimes (often?) becomes necessary to interact with I/O Control
> On Jan 5, 2016, at 11:54 AM, Ryan Lovelett via swift-dev
> wrote:
>
> I'm beginning to try to port some of my existing C code over to Swift
> (you have no idea how excited that makes me). Unfortunately, I've hit a
> stumbling block.
>
> When interacting with some of the system/hardware inter
The Package Installer installs everything into
/Library/Developer/Toolchains/ with
/Library/Developer/Toolchains/swift-latest.xctoolchain pointing to the most
recently installed snapshot.
— Johan
On Tue, Jan 5, 2016 at 5:40 PM, Ryan Lovelett via swift-dev <
swift-dev@swift.org> wrote:
> What is
Response inline:
On Tue, Jan 5, 2016, at 03:12 PM, Xi Ge wrote:
>
> > On Jan 5, 2016, at 11:54 AM, Ryan Lovelett via swift-dev
> > wrote:
> >
> > I'm beginning to try to port some of my existing C code over to Swift
> > (you have no idea how excited that makes me). Unfortunately, I've hit a
>
> On Jan 5, 2016, at 12:32 PM, Ryan Lovelett via swift-dev
> wrote:
>
> Just to be clear though the intent of my question was not to quibble
> with compiler error messages. My real question is how are we meant to do
> systems programming with Swift on Linux if we cannot call ioctl?
In the absen
> On Jan 4, 2016, at 4:35 PM, Michael Gottesman wrote:
>
> The name doesn't really matter to me TBH (and as you can tell I am not an
> expert at such things like Jordan).
>
> I just dislike having this
Sorry for the cut off sentence. John/Jordan, do you have any naming thoughts?
Michael
>
I have posted a blog post to Swift.org that documents the official release
process for Swift 2.2:
https://swift.org/blog/swift-2-2-release-process/
Please feel free to email this list or me directly questions about the process.
In a nutshell:
Swift 2.2 is a mostly source-compatible release
First off thanks for the help.
No doubt I'm doing something wrong. I wish I could help debug my own
problem but I don't really get what @_silgen_name does. That seems like
black magic to me.
That compiled though now it won't link. I've put the code up as a
Gist here[1].
$ swift build Linking Exe
Hi Kevin,
Thanks for your thoughts. In general, I think I’m going to put off thinking
more about the more general extension-shadowing warning until the related
proposal on swift-evolution is decided upon, as decisions made there will
undoubtedly impact what will trigger this warning and how to
11 matches
Mail list logo
