Notes from Swift core team 2016-04-05 design discussion

Great solution for C interop! Eventually, annotations for C language and
API notes could be replaced with such
automatically-generated-manually-correctable bridge files.
We could support a wide range of conversions for @shadowing_c, such as
convertion of IUO to optional or unwrapped type.
There could also be a CBridgeable protocol (like ObjectiveCBridgeable) to
convert Swift data types to ones imported from C. @shadowing_c should
support such convertions.
Better yet, just rename ObjectiveCBridgeable to Bridgeable, and call new
annotation @shadowingImport. Support for other languages, for example, C++,
can theoretically be added later.

I don’t think the notes were conveying a decided-upon solution, so much as a fervent discussion which did not yet yield a conclusion. If you have an idea of how to address this, could you put together a draft?

···

On Apr 6, 2016, at 3:39 AM, Антон Жилин via swift-evolution <swift-evolution@swift.org> wrote:

Great solution for C interop! Eventually, annotations for C language and API notes could be replaced with such automatically-generated-manually-correctable bridge files.
We could support a wide range of conversions for @shadowing_c, such as convertion of IUO to optional or unwrapped type.
There could also be a CBridgeable protocol (like ObjectiveCBridgeable) to convert Swift data types to ones imported from C. @shadowing_c should support such convertions.
Better yet, just rename ObjectiveCBridgeable to Bridgeable, and call new annotation @shadowingImport. Support for other languages, for example, C++, can theoretically be added later.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution