lemme in@lemm.ee to Programming@programming.dev · 4 days agoThe US government wants devs to stop using C and C++www.theregister.comexternal-linkmessage-square77fedilinkarrow-up1214arrow-down118
arrow-up1196arrow-down1external-linkThe US government wants devs to stop using C and C++www.theregister.comlemme in@lemm.ee to Programming@programming.dev · 4 days agomessage-square77fedilink
minus-squareScreaminOctopuslinkfedilinkEnglisharrow-up5·3 days agoIn my understanding, you can’t interface with the C abi without using an unsafe block.
minus-squarecalcopiritus@lemmy.worldlinkfedilinkarrow-up1arrow-down1·2 days agoYou can just use an unsafe block though. Or make a thin wrapper that is just safe functions that inside just have an unsafe block with the C ABI function. Even if rust had a stable ABI, you would still need that unsafe block.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up1·3 days agoI think there are some crates that wrap the unsafe code for you, e.g. https://github.com/rodrimati1992/abi_stable_crates/ (I haven’t ever tried it).
In my understanding, you can’t interface with the C abi without using an unsafe block.
You can just use an unsafe block though. Or make a thin wrapper that is just safe functions that inside just have an unsafe block with the C ABI function.
Even if rust had a stable ABI, you would still need that unsafe block.
I think there are some crates that wrap the unsafe code for you, e.g. https://github.com/rodrimati1992/abi_stable_crates/ (I haven’t ever tried it).