On Mon, Jul 11, 2016 at 2:33 PM, Karl Wagner wrote:
> I remember somebody telling me it was, but it was years ago and I'm
> probably remembering it wrong. Fair enough though; I got told on that one
> đ¶
>
> I'm standing by the principle - it shouldn't matter if you're running in a
> simulator or n
I remember somebody telling me it was, but it was years ago and I'm probably
remembering it wrong. Fair enough though; I got told on that one đ¶
I'm standing by the principle - it shouldn't matter if you're running in a
simulator or not. Use a compile flag if you must know, but in g
> On Jul 11, 2016, at 9:50 AM, Karl Wagner via swift-dev
> wrote:
>
> - Also don't like the simulator condition variable. The iOS simulator is
> literally x86 iOS. If there was an x86 iPhone, theoretically your binaries
> would be compatible. The fact that it runs on a simulator instead of a
> On Jul 11, 2016, at 10:50 AM, Karl Wagner via swift-dev
> wrote:
>
> My thoughts:
>
> I don't like the idea of additional qualifiers after OS. Perhaps we could
> rename it something more generic like "SDK" or split the non-common stuff in
> to a seprarate module?
>
> As for the proposal (
My thoughts:
I don't like the idea of additional qualifiers after OS. Perhaps we could
rename it something more generic like "SDK" or split the non-common stuff in to
a seprarate module?
As for the proposal (I know it's too late for Swift 3, but I read it so I might
as well say what i thought ab
> On Jul 7, 2016, at 7:19 PM, Jordan Rose via swift-dev
> wrote:
>
> Finally, in the spirit of âquestion everythingâ, is âenvironmentâ the right
> name for this setting? :-)
Also, is "environment" a name we want to take for this particular feature?
"Environment" is a broad and general word, a
Hi all,
I Agree with Saleem that this is a worthwhile discussion, and I think I agree
with Jordan that word environment seems a little bit wrong to me.
Following the discussion, it feels to me like what we're really concerned about
is libc and ABI. Most of the examples that Saleem gave seems t
Just want to throw this into the discussion:
* https://github.com/apple/swift-evolution/pull/369
Also discussions on -evolution, which do touch on "Apple-like", etc.
* http://thread.gmane.org/gmane.comp.lang.swift.evolution/7516
* http://thread.gmane.org/gmane.comp.lang.swift.evolution/12065
-
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
Hi,
Id like to revive the discussion around OS "variants". I've been doing
some work to bring up Windows without any emulation layer (MSVCRT based) as
a viable host environment. This work is bringing to light the need for
more finer grained OS checks.
Currently, we have the `os` compilation con
10 matches
Mail list logo
