Ethan Fast

Thanks, that looks very promising! Not sure how I missed it when I looked through the library. I'll close this issue once I confirm it's working -- will also try...

I'd also be very excited to see this happen. @SunDoge do gradients associated with the tensors pass between Python and Rust in your prototype?

Thanks @tomhoule, and also for the fast response! Any idea how I can add a type annotation that will make the above work? I did suspect that `ListMarketsId` was what...

Also yes, I'd be more than happy to add an example / contribute some docs after figuring this out completely!

Thank you! This is perfect. I had thought about option (1) but wanted to avoid that approach. Explicitly providing the type on the call is exactly what I was looking...

Right, good thought! That's definitely the plan (and also why I describe the project as about "lightweight function specifications")

Right. But knowing whether a function can be curried (like your example) requires a bit of analysis that I'm not currently doing ;-) Maybe an extra feature later on.

It actually does. See the new example on the readme. Though I agree that the syntax for making the declaration is not ideal: ``` MyObj = { //+ MyObj.test_fun ::...

Also, if you are looking through your fork, you may want to update things... I've already pushed some fairly significant changes/fixes.

Oh, ok. That's a thornier problem. And the private scoping pattern is pretty common... I'll give it some thought.