We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API stability – dynamic libraries (esp OS ones) being able to be both backwards and forwards compatible is an important consideration.
Some things that potentially break the API:
Note that C3 is stable under error changes.
The text was updated successfully, but these errors were encountered:
Mitigating 1:
Mitigating 2:
Mitigating 3:
Mitigating 4:
Sorry, something went wrong.
Feature:
fn void foo() @dynamic;
Can be checked if it is available, and called if it is:
fn void test() { if (foo.available) foo(); }
Roughly this is what it could have been in C:
extern int fooNewFunction(void) __attribute__((dynamic)); int test() { if (!__exists(fooNewFunction)) return -1; fooNewFunction(); }
Under the covers this is added to the client code:
int fooNewFunction(void) { panic(); } __attribute__((noinline) __attribute__((weak)); bool __fooNewFunctionExists __attribute__((weak)) = false ;
Implemented dynamic calls.
lerno
No branches or pull requests
API stability – dynamic libraries (esp OS ones) being able to be both backwards and forwards compatible is an important consideration.
Some things that potentially break the API:
Note that C3 is stable under error changes.
The text was updated successfully, but these errors were encountered: