You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @egallesio !
Not an essential thing, but I thought it would be nice to have a configure option that would turn signature generation early so the user could see signatures of imported libraries/SRFIs and core procedures.
The text was updated successfully, but these errors were encountered:
jpellegrini
changed the title
Optional procedure arity for primitives and library procedures (wishlist)
Optional procedure signature for primitives and library procedures (wishlist)
Sep 3, 2021
I suppose we could also support formals here. Then, the user would opt for either compiling the formals with the C code or not compiling them - that would be a compile-time option. And if the user decides not to include the formals, they should not take any extra space in the generated binary (that's easy to do :)
bonus.stk, other closures (non-primitives) that come with STklos core, libraries and SRFIs:
Also a compilation option, I suppose, that would turn the parameter compiler:keep-formals on or off before compiling those...
Hi @egallesio !
Not an essential thing, but I thought it would be nice to have a configure option that would turn signature generation early so the user could see signatures of imported libraries/SRFIs and core procedures.
The text was updated successfully, but these errors were encountered: