Re: [swift-users] Transition to the Swift Forums -- mailing lists going into suspend mode

[Nicole Jacque via swift-users]

Whoops, that’s swift-infrastruct...@swift.org 
.

> On Jan 17, 2018, at 6:07 PM, Nicole Jacque  wrote:
> 
> Hi All-
> 
> We’re about to start the transition to our new Swift forums and I’ll be 
> setting the mailing lists to suspend mode shortly so we can export/import the 
> mailing list data.  When the forums are open for business (ETA: sometime on 
> Friday) I’ll update the swift.org website and send out one last email to the 
> mailing lists (before retiring them for good) to let you know.  If there are 
> any unexpected delays, I’ll communicate that via the lists as well.  In the 
> meantime, you can still communicate with me and the rest of the Swift 
> infrastructure team if necessary at infrastruct...@swift.org.
> 
> Cheers!
> nicole

___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

[swift-users] Transition to the Swift Forums -- mailing lists going into suspend mode

[Nicole Jacque via swift-users]

Hi All-

We’re about to start the transition to our new Swift forums and I’ll be setting 
the mailing lists to suspend mode shortly so we can export/import the mailing 
list data.  When the forums are open for business (ETA: sometime on Friday) 
I’ll update the swift.org website and send out one last email to the mailing 
lists (before retiring them for good) to let you know.  If there are any 
unexpected delays, I’ll communicate that via the lists as well.  In the 
meantime, you can still communicate with me and the rest of the Swift 
infrastructure team if necessary at infrastruct...@swift.org.

Cheers!
nicole
___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

Re: [swift-users] Cannot pass immutable value as inout argument

[Geordie Jay via swift-users]

Jordan Rose via swift-users  schrieb am Mi. 17. Jan.
2018 um 01:38:

> Oh no, you're right, I'm sorry. You can only do that with arrays at the
> moment. We do have a bug for this already.
>
> Jordan
>

But couldn’t you call it like this:

lgs_notify_params_t(notify: [lgs_notify_did_enter_background])


For exactly that reason?

- Geordie


>
> On Jan 16, 2018, at 16:37, Roderick Mann  wrote:
>
> Xcode can't properly parse the C header to show me the Swift signature,
> but if I try calling it like this:
>
>let p = lgs_notify_params_t(notify: lgs_notify_did_enter_background)
>lgs_notify(self.ctx, p)
>
> I get this error:
>
> Cannot convert value of type 'lgs_notify_params_t' to expected argument
> type 'UnsafePointer!'
>
>
> On Jan 16, 2018, at 13:22 , Jordan Rose  wrote:
>
> You can do this if you don't write '&', which incorporates the caveat that
> you're not passing a stable address. But please file a bug anyway, because
> the diagnostic should tell you that!
>
> Jordan
>
>
> On Jan 16, 2018, at 13:10, Rick Mann via swift-users <
> swift-users@swift.org> wrote:
>
> Is it not possible for Swift to treat C API const pointers as something
> that can take let arguments?
>
>
> LGS_EXPORT bool lgs_notify(struct lgs_context_t* ctx, const
> lgs_notify_params_t* params);
> .
> .
> .
> let p = lgs_notify_params_t(...)
> lgs_notify(self.ctx, )
>^Cannot pass immutable value as inout argument: 'p' is
> a 'let' constant
>
>
> Why isn't the "const" in the C declaration enough to let Swift know it's
> const and just allow it to be a let?
>
> --
> Rick Mann
> rm...@latencyzero.com
>
>
> ___
> swift-users mailing list
> swift-users@swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
>
>
>
>
> --
> Rick Mann
> rm...@latencyzero.com
>
>
> ___
> swift-users mailing list
> swift-users@swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
>
___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

Re: [swift-users] Protocol conformance error

[Nevin Brackett-Rozinsky via swift-users]

Because it would break this:

func foo (c: T, a: U) { c.test(a) }

Nevin


On Wed, Jan 17, 2018 at 2:29 AM, Roshan via swift-users <
swift-users@swift.org> wrote:

> Hi,
>
> Here is some sample code that gives a protocol conformance error in a
> playground:
>
> protocol A {}
> protocol B: A {}
>
> protocol C {
> func test(x: A)
> }
>
> class M: C {
> func test(x: B) {}
> }
>
> Is there a reason why the compiler doesn't infer that ((B) -> ())
> matches ((A) -> ()) because of inheritance?
>
> --
> Warm regards
> Roshan
> ___
> swift-users mailing list
> swift-users@swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
>
___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users