Giulio Canti

@rattrayalex There are some discussions here and there - https://github.com/gcanti/flow-io/issues/19 - https://github.com/gcanti/io-ts/issues/4 Currently there are a bunch of similar libraries I'm aware of and with different goals - [tcomb](https://github.com/gcanti/tcomb) (JavaScript-y,...

Just a clarification: tcomb was born several years ago when static type checking was semi-non existent. Now that we have both Flow and TypeScript personally I'm just interested in IO...

Yeah, but seems just an optimization which btw implies a bit of (albeit basic) static analysis, I think it doesn't worth it to complicate the plugin code for this. In...

The use case is runtime type introspection, that is when you want to read the informations stored in your types. When you write this: ``` js type Credentials = {...

I'm pleased to announce the [next post](https://github.com/gcanti/babel-plugin-tcomb/issues/62) on refinements

Nice! Thanks for the suggestion

> In application we can't access type metadata > > Type system is separate from javascript. Flow or typescript does not help, types as value keys not supported. @zerkalica sorry...

AFAIK there are 2 cases: - `myLib` is a library you own, i.e. it's a submodule of your app or you can import the source code and is typed -...

If `myLib` is a library that exports tcomb types you can have both (static and runtime) if you do this: ``` js // myLib/index.js var t = require('tcomb'); exports.User =...

> the most common solution for this problem is the usage of a Reader Many people prefer to inject the dependencies explicitly, so another option is using some kind of...