> In safe mode, C3 checks array bounds, null dereferences, shifts, casts, unwraps and so on, and each check that can fail needs code to report the failure with a message, a file, a function and a line
It's basically debug information. Why not putting it into a separate file?
> In safe mode, C3 checks array bounds, null dereferences, shifts, casts, unwraps and so on, and each check that can fail needs code to report the failure with a message, a file, a function and a line
It's basically debug information. Why not putting it into a separate file?
> These are zip archives with C3 sources, headers, prebuilt binaries per target and a manifest.json
What's the point of distributing prebuilt binaries? It seems to be a point of failure in case of an ABI change.
Because people like me like prebuilt binaries if they work an it keeps me from having to deal with some new clusterfff build system
Awesome! Great work