Provide mechanism for intent objects to document (and perhaps enforce) types for inputs and outputs

[itamarst]

In a language with a good type system you can be sure that the result you swapped in as part of a test vaguely make sense. In Python it's easy to write tests using mocks or resolved values where you end up testing against return types that don't match what the real function returns.

Perhaps intent objects should have a way document or provide validation functions for the return types and callable arguments. Then tests that use resolve_effect (as well as those that test the intent itself) can automatically ensure the tests are using the correct types.

[radix]

The title of this ticket doesn't really make sense as a bug. Can you please rewrite it?

[radix]

I'm sorry I didn't notice this change when you made it, I don't think github sent me a notification :-(

Anyway, that title is a lot more helpful, thank you. However, I would suggest that this is probably something that a separate library should tackle. It should be easy enough to apply a static-typing wrapper to your intent objects and perform implementations. Does that sound reasonable?

[wilbertom]

@itamarst I was playing with the idea of doing this in python a while back. I haven't really shown anyone though. You can do things like strict type checking for example is_list, or you can do other things that mimic Haskell's type classes for example is_iterable. Sorry if I misinterpretted your issue.

https://github.com/wilbertom/contracts

[radix]

You may also want to check out MyPy, which adds static typing to Python.

I'll close this issue for now, since I think it's clear this is the responsibility of other libraries.