Christoffer Lerno
Christoffer Lerno
This issue is tracking full ABI compliance for all targets, not just the initially supported ones. - [x] SysV x64 - [x] Win64 - [x] RISCV - [x] Aarch64 -...
It should be easy to copy varargs from a macro, e.g. macro foo(args...) { call_func(...args); }
See http://www.c3-lang.org/types/#anonymous-structs Alternative to func void set_coordinates(struct { int i; int j; } coord) { ... } Would be something like: struct Vec2 { int x, int y } //...
It is possible to set require / ensure at the caller site. For the parameters, this can add a level of static checking.
Textual includes are described here: http://www.c3-lang.org/modules/#textual-includes Consider whether they should be added or perhaps textual include should work differently.
Suggestion: keep builtins in a `std::builtin` module. They are provided as macros and not functions.
If a private function is not called outside of its module it should be marked as such, since private imports are only possible if the source is available, which means...