> I think I may be similarly misunderstanding your proposal; your intention 
> then is to import the type as an enum with raw value (to facilitate the 
> conversion to/from the C code) but without exposing that raw value on the 
> Swift side?
> 
> In that case I think I’m in favour.

Me too.

But perhaps not through the originally proposed syntax. I don't think this is 
an extension — it's more of an external annotation on C code, something that we 
don't currently support for user code. (My understanding is that they have it 
implemented for Apple frameworks.)

Perhaps, with Swift 3 going Linux, with should expose the ability to annotate 
external code to the users? And enum importing could be a part of that.

A.


_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
  • [swift-evolution] Promote... Carlos Rodríguez Domínguez via swift-evolution
    • Re: [swift-evolution... James Campbell via swift-evolution
      • Re: [swift-evolu... Carlos Rodríguez Domínguez via swift-evolution
        • Re: [swift-e... Paul Ossenbruggen via swift-evolution
          • Re: [swi... Carlos Rodríguez Domínguez via swift-evolution
            • [sw... Carlos Rodríguez Domínguez via swift-evolution
              • ... Andrey Tarantsov via swift-evolution
                • ... Carlos Rodríguez Domínguez via swift-evolution
            • Re:... Haravikk via swift-evolution
              • ... Carlos Rodríguez Domínguez via swift-evolution
              • ... Andrey Tarantsov via swift-evolution
                • ... Carlos Rodríguez Domínguez via swift-evolution

Reply via email to