-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
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
Implement VariadicAny
around pg_sys::FunctionCallInfo
#1428
Comments
FnArgs<'a>
or FnCallCx<'a>
around pg_sys::FunctionCallInfo
?
This is made particularly relevant because pgrx has a neat trick where, if the final argument is |
FnArgs<'a>
or FnCallCx<'a>
around pg_sys::FunctionCallInfo
?FnArgs<'a>
or FnCallCx<'a>
around pg_sys::FunctionCallInfo
This is no longer a "consideration": I have identified this as actually very important to moving forward, because |
Also this would be useful for allowing a |
FnArgs<'a>
or FnCallCx<'a>
around pg_sys::FunctionCallInfo
VariadicAny
around pg_sys::FunctionCallInfo
The current
FunctionCallInfo
is unnecessarily unsafe when presented as an argument to a function. We could have a safe wrapper around it that only exposes sensical behaviors when it is presented as an argument to a function. This could also simplify everything we currently do...pg_getarg
, etc.The text was updated successfully, but these errors were encountered: