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
Our compiled query API surface is nice and generic, accepting up to 16 generic parameters (e.g. CompileAsyncQuery). However, these generic methods seem to call into non-generic methods which accept params object[], so that an array parameter is allocated and all parameter values are boxed.
Actually flowing generic parameters all the way into QueryContext (and from there into a generic DbParameter, if we ever get one), is likely to require quite a bit of work. In the meantime we can at least avoid the array allocation on every execution.
The text was updated successfully, but these errors were encountered:
Our compiled query API surface is nice and generic, accepting up to 16 generic parameters (e.g. CompileAsyncQuery). However, these generic methods seem to call into non-generic methods which accept
params object[]
, so that an array parameter is allocated and all parameter values are boxed.Actually flowing generic parameters all the way into QueryContext (and from there into a generic DbParameter, if we ever get one), is likely to require quite a bit of work. In the meantime we can at least avoid the array allocation on every execution.
The text was updated successfully, but these errors were encountered: