Results 40 comments of djerius

Mistake in title (fixed): it's coercion_generator, not constraint_generator.

BTW, this is rather low priority, as there's a simple (rather less convoluted) workaround: ``` sub foo (@args){ state $signature = signature( named => [ head => Str, uri =>...

That does move the logic out of the caller, but it moves the setting of defaults for this parameter out of the signature and into the body of the subroutine....

Agreed, it's just that there are older modules which don't support it yet, so the ability to add options to Build.PL would be useful.

@chrestomanci, Sorry for not initially providing an example. Since GitHub has no means of uploading files to issues, I stuck a shar file ( haven't used shar since usenet days!)...

@chrestomanci, I've tried your branch and it works. Thanks, Diab

This would be nice (it would be Moo compatible), except that as things are currently written, it would prevent read-only custom accessors. They'd have to be generated within Class::Tiny itself.

Here's my horrible work around. Force a share static install by using the PkgConfig plugin and an impossible exact version: `plugin PkgConfig => ( pkg_name => 'qhullstatic_r', exact_version => 0...

Thanks for thinking about this. For now I've hacked my config loading code so that if it sees a `+` sign in the file name it knows it's two files...