George Lester

That's correct, this is the same problem as in #61, see [this comment](https://github.com/Knetic/govaluate/issues/61#issuecomment-321947672) for some more explanation. This is definitely a bug, but I don't have a timeline for fixing...

I agree, I've been a little uncomfortable with the automatic-parsing. It treats literal strings differently than parameter strings, and while the auto-parsing is useful in dead-simple expressions (such as `foo...

Yes, that's the behavior. The parser treats all unescaped strings of characters as a variable - unless it finds a function with that name in the function map. This isn't...

This happens because the parser doesn't differentiate between arrays passed as parameters, and an array made with separators (such as `(1, 2, 3)`). They both end up as `[]interface{}`, and...

I hadn't commented on this when i first read it, because i was tackling other problems and didn't have a good answer. ... that said, I still don't have a...

It doesn't support them in such a format, but the result of `1e5` (100,000) can be expressed as `10**5`, where `**` is the exponentiation operator. Internally, the operation is elided...

This might mean a couple different things; If you want to convert the logic of an expression into a SQL query, that's more or less supported with [ToSQLQuery](https://godoc.org/github.com/Knetic/govaluate#EvaluableExpression.ToSQLQuery). The other...

That approach is probably the best to get you unstuck for now, yeah. There's no technical drawback to it - I hadn't added map support yet because I'd preferred to...