Ryan Paul @ RethinkDB brought to light there are some issues with PowerShell + Lambdas (ReqlFunction*) type resolution. After some light debugging, I suspect this is a problem with Newtonsoft.Json not playing nice with the PowerShell type system.
Additionally, our [bracket] parameterized property overloads may have something to do with self-recursion exceptions.
Also, PowerShell lambdas seem to be some kind of Delegate type, but not a strong enough type to pass the ReqlFunction* checks in Func.FromLambda(Delegate) term. I got a few exceptions that read Arity of ReqlLambda not recognized!. Hmm.
Re: F#
DJS: "The biggest gotcha I've encountered so far is with .Filter. The implicit conversion from func to ReqlFunction1 doesn't happen, so it uses the obj overload, which doesn't work. I've got another repo (myWebLog) that has some examples using filter, indexes, etc."
Ryan Paul @ RethinkDB brought to light there are some issues with PowerShell + Lambdas (
ReqlFunction*) type resolution. After some light debugging, I suspect this is a problem withNewtonsoft.Jsonnot playing nice with the PowerShell type system.Additionally, our
[bracket]parameterized property overloads may have something to do with self-recursion exceptions.Also, PowerShell lambdas seem to be some kind of
Delegatetype, but not a strong enough type to pass theReqlFunction*checks inFunc.FromLambda(Delegate)term. I got a few exceptions that readArity of ReqlLambda not recognized!. Hmm.Re: F# DJS: "The biggest gotcha I've encountered so far is with .Filter. The implicit conversion from func to ReqlFunction1 doesn't happen, so it uses the obj overload, which doesn't work. I've got another repo (myWebLog) that has some examples using filter, indexes, etc."
/cc @segphault
:car: :bluecar: [**"Let the good times roll..."**_](https://www.youtube.com/watch?v=7BDBzgHXf64)