Got it. Seems like, in this case, this is the best (i.e. only) way to do things.
For the general case, I’m not sure what the current “no new language” policy
states, but I would favor some kind of amendment that said “…unless it’s the
only way to do things because you’re calling out to something
> On Jun 9, 2021, at 11:31 AM, Geoff Garen wrote:
>
> In this specific case
>
> What is the API we’re trying to call into?
This is calling into the GroupActivities.framework API which was announced at
WWDC this week.
> Is using Swift the only way to call into it?
This was true
In this specific case
What is the API we’re trying to call into?
Is using Swift the only way to call into it?
Is there any way to reduce the use of Swift to only the calls into it,
and not the surrounding objects (which all seem to be marked @objc anyway)?
Thanks,
Geoff
Hi Jer,
I think it sounds like a reasonable rule to allow Swift for bridging purposes
only, with the caveat that we should prefer Objective-C/C where it can be used.
The one other place that Swift seems reasonable for WebKit is in the definition
and refinement of Swift bindings to WebKit’s publ
4 matches
Mail list logo
