Andrew Bashkatov

Also added the ability to use globs (wildcards) in include paths, e.g. `#include user/*.cfg`.

Ok. I think you are right and that sounds good to me. Let it be only one directive `#include` then, which acts in the strict manner like `#require`.

@robfig I fixed it. There is only one directive `#include` here.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

We were discussing that in the issue #14 but conversation stuck. IMO the syntax becomes very complex and application should have hardcoded default values for missing env variables.

Regarding to strongly/weekly typed I'm thinking of two options: - User asks when strogly typed value is required, e.g. `$"FOO"::int!` - strong, `$"FOO"::int` - weak. - User asks when weakly...

If we leave it public then we should track if the user issued it already and that is one more field in FtpStream struct. But that is not really a...

`run.Parallel` returns `floc.ErrMultiple` in case of any error occurs. Try "casting" the returned error to that type and access the list of errors here. ```go flow := run.Parallel(fail("asd"), fail("qwe")) result,...

Probably `ErrMultiple` lacks some implementations of interfaces required by `errors` package so `errors.As` cannot cast the error. Try casting explicitly `e, ok := err.(floc.ErrMultiple)`. Anyway I would recommend using idiomatic...