Skip to content
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

Unify IAsyncTexlFunction #2751

Open
MikeStall opened this issue Nov 25, 2024 · 0 comments
Open

Unify IAsyncTexlFunction #2751

MikeStall opened this issue Nov 25, 2024 · 0 comments

Comments

@MikeStall
Copy link
Contributor

MikeStall commented Nov 25, 2024

We shouldn't have 5+ variations of IAysncTexlFunction plus AsyncFunctionPtr delegate.

We should be able to remove this branch in EvalVisitor and have it be a single dispatch.

IReadOnlyDictionary<TexlFunction, IAsyncTexlFunction> extraFunctions = _services.GetService<IReadOnlyDictionary<TexlFunction, IAsyncTexlFunction>>();

Ideally, unify across:

  1. builtin invocations
  2. UDFs
  3. Custom Functions (ReflectionFunction)

Broader design things to consider:

  • can we unify with StandardErrorHandlingAsync?
  • can we still follow Least-privilege? At least with many interfaces, the functions are describing statically which subset of functionality they need.

This is an engineering hygiene issue. Need to come up with a good design.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant