[webkit-dev] Use of Swift (for bridging) in the WebKit project

[Jer Noble]

Hi all!

We're working on some new features that currently use APIs exposed through Swift. We have not yet approved writing and committing WebKit code in Swift, given runtime, library, and just plain mental overhead that comes with adding a new language to the project. But I'd argue that doing so for the purpose of allowing existing C++ code to call into Swift APIs is probably not terrible.

Should we relax our "no new language" policy, only for the purposes of allowing our core language code to call into APIs in Swift?

(ref: https://bugs.webkit.org/show_bug.cgi?id=226757)

Thanks, and look forward to hearing from everyone,

-Jer