<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jul 11, 2016 at 2:33 PM, Karl Wagner <span dir="ltr"><<a href="mailto:razielim@gmail.com" target="_blank">razielim@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><span style="background-color:rgba(255,255,255,0)">I remember somebody telling me it was, but it was years ago and I'm probably remembering it wrong. </span>Fair enough though; I got told on that one 😶</div><div><br></div><div>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 general I disagree with a compiler flag for determining the runtime platform for two platforms with the same API and triple.</div><span class="HOEnZb"><font color="#888888"><div><div style="font-family:'Helvetica Neue','Helvetica',Helvetica,Arial,sans-serif;font:'-apple-system-body'"><br></div></div></font></span></div><div><span class="HOEnZb"><font color="#888888"><div>Karl</div></font></span><div><div class="h5"><div><br><blockquote type="cite" style="margin:1ex 0 0 0;border-left:1px #ccc solid;padding-left:0.5ex"><div>On Jul 11, 2016 at 11:26 PM, <<a href="mailto:gparker@apple.com" target="_blank">Greg Parker</a>> wrote:<br><br></div><div><br><div><blockquote type="cite"><div>On Jul 11, 2016, at 9:50 AM, Karl Wagner via swift-dev <<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>> wrote:</div><br><div><div><div>- 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 real device is not such a vital distinction (or shouldn't be) that we need integrate it in the language. What would we do in the future if there ever was a real x86 iOS target?</div></div></div></blockquote><br></div><div>The iOS simulator is not literally x86 iOS. It has changed ABI in incompatible ways in the past and reserves the right to do so in the future. Any real x86 iOS would have a real ABI which would likely differ from today's simulator.</div><div><br></div><div><br></div><div>-- </div><div>Greg Parker   <a href="mailto:gparker@apple.com" target="_blank">gparker@apple.com</a>   Runtime Wrangler</div></div></blockquote></div></div></div></div></div></blockquote></div><br>Well, the name that I went with was environment was derived from the fact that it was based on the "environment" component of the "triple". That said, an alternative idea is to make a more invasive change:</div><div class="gmail_extra"><br></div><div class="gmail_extra">`host(...)`: where we can actually do a more target specific component matching. Something like:</div><div class="gmail_extra"><br></div><div class="gmail_extra">#if host(Windows, msvc)</div><div class="gmail_extra">#elseif host(Linux, musl)</div><div class="gmail_extra">#elseif host(iOS, ARM)</div><div class="gmail_extra">#endif<br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Saleem Abdulrasool<br>compnerd (at) compnerd (dot) org</div>
</div></div>