davisvaughan / cbuild Goto Github PK

And then delete it

If we make ... the first argument then we can force named arguments for the options. We can also generate good error messages for any typos or incorrectly options by capturing anything that ends up in the dots

https://github.com/r-lib/cleancall/blob/f7fd3ae996ac890dd1fc8ef109d3a6ac48968675/src/cleancall.c#L63

For example, you register a callable with a function pointer as argument, like done in cleancall

The generated callable forward declaration is wrong for callable() lines because it assumes they all have SEXP arguments. If we record the types while parsing we can use them here to generate the correct declaration https://github.com/DavisVaughan/vctrs/blob/69f839f41975871edfd40604b71ea44938f9061a/src/init.c#L188

For non-hidden callables. What is the "preferred" way to write the API file? There are two main methods, one that writing r extensions recommends, and one that we do in vctrs that requires slightly more user effort. Maybe support both with some way to specify that you want to use one or the other for the entire package? Maybe something in the DESCRIPTION file like roxygen2 does?