Christophe PLAT

No, async / await is not supported, and probably never will be. When you write an async method, the compiler performs a LOT of things (creating a class to hoist...

Relevant documentation : https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/patterns Relevant specifications : https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/expressions#121212-the-is-operator We can probably focus on the `is` operator, and ignore the `switch` statement and expression.

Yes, it's fixed via #233, by setting a variable named `"this"`. Full example: ```c# var target = new Interpreter(); target.SetVariable("this", new { FirstName="Homer", LastName="Simpson"}); target.Eval("FirstName").Dump(); ```

Yes, all the `Parse` methods could all be merged into a single one (and in the end, they all call the same `ParseRawExpression` method), but the existing methods are part...

I don't think we need a new Interpreter class, because most of the Parse overloads are just syntaxic sugar over the ParserResult class (they could be moved to dedicated extension...

Trying to multiply a decimal with a double is not valid C#, so you need a conversion.

I confirm: we connect to our Influx host via https, and it works perfectly (and has worked perfectly for several years now :)).

Hi @holdenmai, thanks for the investigation, that's really interesting! FYI, if you want to go deeper, you can read [this section of the C# language specifications](https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/conversions#105-user-defined-conversions). I'm not sure we...

Oops I didn't see the draft status

We're also seeing poor performances with Flux when using `aggregateWindow`: the Flux version is about 30 times slower than the equivalent InfluxQL query with `GROUP BY(time)` (InfluxDB 1.8.2): 17s for...