James Reeves

Thanks for the PR. I think this is a useful feature to have, but I think the proposed design is too complex (in the "Simple Ain't Easy" sense of the...

I think I'd still prefer `derived-keys` over a keyword specification. Using `multi-spec` might be a good idea; I'll take a look at how it operates. The functions that do one...

I'd rather a `derived-keys` function is used over a `::configuration` keyword, as then we can supply required keys via a `:req` option. As un-namespaced keywords cannot be derived, there is...

`refset` is used to generate a set of refs. It's useful for times when you want to reference all keys that derive from a base key, either because you want...

I haven't received any more requests for compatibility with spec. I think it would be nice to have, but somewhat complex to implement, so it hasn't been a priority of...

This sounds like a broader problem than Integrant. It encompasses any library that makes use of namespaced keywords, including spec. There has been some talk around introducing a way of...

I think I'd rather have any pre-processing of the configuration as an explicit step.

> I believe it would be much simpler to dispatch the configuration based on specific key in the configuration map itself. Both defining and referencing configuration would be much simpler....

Originally, this is what `build` was for, as `init` is just a wrapper around that. But `resume` is a little more complex. I'll need to consider what the best way...

Thanks for the PR. This wasn't exactly the design I was thinking of, but I'll need to give this more thought before I commit to anything. This may take at...