<@U3SRWNXQB> I wonder if your above commit represe...
# kotlin-nativej
jmullin
02/10/2019, 7:06 PM@svyatoslav.scherbina I wonder if your above commit represents some hope that restriction is going away, or has been removed? 😃
s
Sam
02/10/2019, 7:11 PMIt could be part of master but not released yet. Does the commit come before or after the 1.3.20 tag? I’m on mobile now and it’s hard to navigate through the commit history in the mobile site.
j
jmullin
02/10/2019, 7:20 PMYeah, also on mobile here but I’ll do some archaeology later to see. Hopefully!
g
gildor
02/11/2019, 4:55 AMAccording to GitHub this commit available only in master, so I believe it not released
gildor
02/11/2019, 4:58 AMProbably this commit also related to this interop change (but also not released yet)
https://github.com/JetBrains/kotlin-native/commit/6ca196399a245821887c019898d80f5f7f8931c8
s
svyatoslav.scherbina
02/11/2019, 7:46 AMExactly. Callbacks returning structs are supported in master.
j
jmullin
02/11/2019, 3:24 PMFantastic! This is the feature that was keeping me off K/N, so I’m really excited. Thanks for the info!
👍 1
n
napperley
02/11/2019, 8:55 PMThat commit ( https://github.com/JetBrains/kotlin-native/commit/6ca196399a245821887c019898d80f5f7f8931c8 ) will make it significantly easier to have Kotlin Native ported to additional platforms with libffi being dropped as a dependency. Especially when using C APIs that make use of C varargs (widely used on embedded platforms).
👌 1
s
Sam
02/11/2019, 9:31 PMOnce libffi is gone is there anything preventing usage of K/N on bitcode only platforms such as the Apple TV or Apple Watch?
s
svyatoslav.scherbina
02/12/2019, 8:04 AMDifferent LLVM versions maybe.
Bitcode is supposed to be generated by patched Apple LLVM version shipped with Xcode. The difference between versions is to be investigated.
s
Sam
02/12/2019, 11:53 AMSadly that’s not a topic easily Googled. When I looked I mostly found articles about bitcode from 2015.
➕ 1
2 Views