evalexpr
evalexpr copied to clipboard
ISibboI
A powerful expression evaluation crate 🦀.
I would like to expose variables (not functions) to the expressions that are not simple data items but I cannot find a way to do it . Specifically - I...
It makes sense in my use case where hex inputs are expected to be $fd This is trivial to implement, I can do a PR. All your tests pass But...
This PR adds two features `decimal_support` and `empty_is_null`. # Feature `decimal_support` #115 The `decimal_support` feature enables support for Decimal float type calculation using the `rust_decimal` library. Note that due to...
Change the Display instance for Node. Previously it printed a simple pre-order traversal, which was sometimes ambiguous because e.g. for nested n-ary functions it wasn't clear which things were arguments....
I couldn't find anything related to this, so I think nobody has asked for it. Do you plan to introduce the [] operator for the array type? I feel like...
Is it possible to access variables in context by dot notation like this? ```rs use evalexpr::*; fn main() { let ctx = context_map! { "a" => context_map! { "b" =>...
Hi Mr. @ISibboI I poke around the threads and find related issue: https://github.com/ISibboI/evalexpr/issues/117, this is similar to what I am looking for, I will make a pull request if you...
Right now when parsing a literal fails, evalexpr simply assumes it is supposed to be an identifier. We should introduce the basic rule that identifiers need to start with a...
