News for hackers. Stuff that matters.

A comment on Porting a historic Python2 module to Python3. Parent comment

Re:Porting a historic Python2 module to Python3 by kbenson on Thursday July 27, 2017 @04:02PM (#14868900)
Isn't Swift compiled? I'm not sure it's relevant to the specific problems faced here, unless a library written and compiled in earlier versions of Swift won't be usable in a Swift 4 project.
[ Parent | on HN ]
Re:Porting a historic Python2 module to Python3 by ori_b on Thursday July 27, 2017 @04:11PM (#14868992)
That's the case. Swift is currently not abi compatible, so libraries compiled with one Swift version only work with that version.
[ Parent | on HN ]
Re:Porting a historic Python2 module to Python3 by kbenson on Thursday July 27, 2017 @05:24PM (#14869733)
Ah, I see. I assume you could compile to a C compatible library, but they you would have to deal with marshaling costs where the types mismatch, correct?
[ Parent | on HN ]