Re: Swift functions in render callback
Re: Swift functions in render callback
- Subject: Re: Swift functions in render callback
- From: Chris Adamson <email@hidden>
- Date: Wed, 15 Mar 2017 08:07:49 -0400
On Mar 15, 2017, at 7:21 AM, Nikolozi Meladze <email@hidden> wrote:
Necessary, but I don’t believe it’s sufficient. By analogy, you could write Objective-C code without ARC, hold a pointer to an Objective-C object, call its objc_msg_send() directly, and you’d still be outside the render-thread rules (because the Objective-C runtime itself is unsafe to use in an RT context… see WWDC 2015 session 508).
FWIW, a thought experiment about when you’ll be able to write v3 Audio Units in Swift was part of a talk I did at Forward Swift a few weeks back. It seems like both ABI stabilization and the ownership model are required, and even then it’s not clear that they’re sufficient. However, audio rendering is the specific case that the ownership manifesto calls out in its preamble, so it’ll provide an interesting test of how many years it’ll be (if ever) before you can do these kinds of things in Swift.
—Chris
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden