I was wondering how that would work when consuming a compiled/binary library (either statically or dynamically): BMI files are the compilation artefact representing module's interfaces. They're used by the compiler when importing modules. Would they need to be included as side-carts when distributing a library in binary/compiled form? If so, how would that work across compiler versions, given how there's no binary-compatability guarantee for that?
![[Full] 4 ต่อ 4 Celebrity EP.920 | 3 พ.ย. 67 | one31](http://i.ytimg.com/vi/KwiW2M_kAg4/mqdefault.jpg)
I was wondering how that would work when consuming a compiled/binary library (either statically or dynamically):
BMI files are the compilation artefact representing module's interfaces.
They're used by the compiler when importing modules.
Would they need to be included as side-carts when distributing a library in binary/compiled form?
If so, how would that work across compiler versions, given how there's no binary-compatability guarantee for that?