Apparently this was done intentionally. The rationale given is that we don't want to allow non-safe C to be used in fil-C programs. Fair enough.
But why should we prevent fil-C programs to be used from Rust (or C, for that matter)?
I don't understand much about compilers, but I guess allowing one would also allow the other? i.e. it's not possible to make fil-C ABI compatible with C (so that it can be more easily called), while also not letting you use call C from it?
Georgelemental 3 minutes ago [-]
It's also because Fil-C calls need to carry along a bunch of extra information, to support the safety checks
Wleddzig 25 minutes ago [-]
Increment the "fell for fil-C propaganda" counter.
This article fully concede's Filip's categorically incorrect definitions regarding memory safety, accepting them as true.
I don't want extern "fil-C", it legitimises Filip's bad-faith trolling and hypocrisy as an acceptable way to operate a software project, and makes rust dependent on his single ISA single OS fork of clang which is actually just granular ASAN with atomic instrumentation code and a garbage collector, fluffed up with fil's marketing terminology "invisicaps" etc.
https://fil-c.org/runtime
Apparently this was done intentionally. The rationale given is that we don't want to allow non-safe C to be used in fil-C programs. Fair enough.
But why should we prevent fil-C programs to be used from Rust (or C, for that matter)?
I don't understand much about compilers, but I guess allowing one would also allow the other? i.e. it's not possible to make fil-C ABI compatible with C (so that it can be more easily called), while also not letting you use call C from it?
This article fully concede's Filip's categorically incorrect definitions regarding memory safety, accepting them as true.
I don't want extern "fil-C", it legitimises Filip's bad-faith trolling and hypocrisy as an acceptable way to operate a software project, and makes rust dependent on his single ISA single OS fork of clang which is actually just granular ASAN with atomic instrumentation code and a garbage collector, fluffed up with fil's marketing terminology "invisicaps" etc.