-
Notifications
You must be signed in to change notification settings - Fork 59
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
Port lambda compilation to original NCalc as plugin #112
Comments
It would be great if the ncalc community could unite behind a single implementation. Having ncalc/ncalc, sklose/ncalc2, and ncalc/ncalc-async causes confuses which is apparent on some of the issue boards in the various repos. I think this repo adds more than support for linq expressions. The difference in the EvaluationOptions might be a reasonable place to start. |
There are some difference between NCalc and NCalc2 with EvaluationOptions (now it's ExpressionOptions), welcome to contribute ncalc/ncalc#188 ! |
@Bykiev @david-brink-talogy looks like the PR ncalc/ncalc#188 is about to land. What do you think should be the future of this project? It seems all features that were added here have been ported. I am leaning towards archiving the project and updating the README file with a pointer to ncalc/ncalc. Does anybody see any value in keeping this project alive? |
I think after the release of |
Might be good to get insight from the PanoramicData team since it has a dependency on this package. Unfortunately it doesn't seem like I can properly mention @davidnmbond. |
PanoramicData still using v2.2.110 |
As all features from NCalc2 were moved to NCalc project this repo can be archived. Welcome to contribute! |
The original NCalc version was moved to Parlot parser. Now the DI and Plugins are supported. As many features are just backported here I'd suggest to implement the core feature - compilation of expression to CLR Lambda as Plugin.
@david-brink-talogy, @sklose what do you think?
The text was updated successfully, but these errors were encountered: