We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
expr.Eval
The logic to evaluate an expression against a store is duplicated in several programs.
We are dealing directly with the antonmedv/expr library, which we believe is problematic for unified expression expansion.
antonmedv/expr
I think we need to organize the use cases for the process of evaluating expressions, clarify who is in charge of the logic, and do some refactoring.
The text was updated successfully, but these errors were encountered:
Hi @k2tzumi
We have integrated the functions related to the expr package in eval.go
expr
I think this has achieved a certain level of success, but what do you think?
Sorry, something went wrong.
@k1LoW
Yes. I think we have been able to integrate. Thank you for your response!
No branches or pull requests
The logic to evaluate an expression against a store is duplicated in several programs.
We are dealing directly with the
antonmedv/expr
library, which we believe is problematic for unified expression expansion.I think we need to organize the use cases for the process of evaluating expressions, clarify who is in charge of the logic, and do some refactoring.
The text was updated successfully, but these errors were encountered: