> On Jul 7, 2016, at 5:26 PM, John McCall wrote:
>
> Suppose we are calling a function that is generic over T, where T: AnyObject.
> This comes up when e.g. calling an initializer for an ObjC generic class.
>
> Today we allow conversions from [String] to [NSString], String to NSString,
> and
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
-
> On Jul 7, 2016, at 17:26, John McCall via swift-dev
> wrote:
>
> Suppose we are calling a function that is generic over T, where T: AnyObject.
> This comes up when e.g. calling an initializer for an ObjC generic class.
>
> Today we allow conversions from [String] to [NSString], String to N
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
Suppose we are calling a function that is generic over T, where T: AnyObject.
This comes up when e.g. calling an initializer for an ObjC generic class.
Today we allow conversions from [String] to [NSString], String to NSString, and
[String] to [T], but we do not allow a conversion from String t
I am preparing a fix. Its in this PR:
https://github.com/apple/swift/pull/3406
Michael
> On Jul 7, 2016, at 4:30 PM, David Farler wrote:
>
> Adding +Michael Gottesman who changed some things around in this file. I also
> hit this with:
>
> build-script -r --debug-swift -x
>
> CMake Error at
Adding +Michael Gottesman who changed some things around in this file. I also
hit this with:
build-script -r --debug-swift -x
CMake Error at cmake/modules/SwiftSharedCMakeConfig.cmake:67 (message):
Unsupported imported target type MODULE_LIBRARY
Call Stack (most recent call first):
cmake/mod
And most fix-its make good starter bugs, so it’s good to label them that way!
— Harlan
> On Jul 7, 2016, at 1:31 PM, Joe Groff via swift-dev
> wrote:
>
>
>> On Jul 7, 2016, at 10:19 AM, Erica Sadun via swift-dev
>> wrote:
>>
>> Where is the best place to request fixits? bugs.swift.org or o
> On Jul 7, 2016, at 10:19 AM, Erica Sadun via swift-dev
> wrote:
>
> Where is the best place to request fixits? bugs.swift.org or on this list?
>
> I've been porting a lot of code to Swift 3 and finding a lot of issue and no
> before you ask, I stupidly did not write them down as I went and
Hi,
I am running the second preview of macOS Sierra and am attempting to build
swift. LLVM and cmark built successfully, but swift failed during the
configuration stage with the error message
Unsupported imported target type MODULE_LIBRARY
I hacked the cmake file by bypassing the conditional che
Where is the best place to request fixits? bugs.swift.org or on this list?
I've been porting a lot of code to Swift 3 and finding a lot of issue and no
before you ask, I stupidly did not write them down as I went and I now wish I
had -- I just was on a deadline and needed the code ported and wor
13 matches
Mail list logo
