shadowcat-mst

On Tue, Jul 23, 2013 at 06:29:28AM -0700, Manuel Simoni wrote: > The wat-js license is the "MIT license". I now realized that that is an ambiguous term. In any...

(if you decide issues are a stupid way to communicate please just tell me how you'd rather do so - seems to be a reasonable-ish approach so far)

One of the nice things from my POV is that I can do things like use my http://p3rl.org/curry module to do: ``` [ def frob-foo [foo curry::frob]] [ frob-foo 3...

Adding in auto-coderef calling and using perl's operator overloading to make it possible to go the other way - i.e. an Apv overloads to a coderef that combines the internals...

On Tue, Jul 09, 2013 at 04:42:59AM -0700, Manuel Simoni wrote: > Standardizing across JS and Perl -- sounds like the definition of hell to me ;-) I was planning...

(response to deleted comment elided) @nrdvana @stigtsp @sjn I'm happy thrashing this out and taking it to PSC once we've got a decent idea what we're doing (this is an...

@nrdvana sorry for the typo - also, I don't understand, given I proposed something to do as -well- as the warning you'd implemented I don't see why your warning wouldnt...

That sounds reasonable but in that case why not let the accessor return undef so users can perform that check as well? The bit I didn't like was the part...

it's called a decorator, not a wrapper, usually. plus I'd make ->new do the wrapping, otherwise ->wrap is going to have to produce a new object. nothing wrong with FooWrapper->new(service...

your argument wrt multiservice is incoherent; I think you're imagining problems that don't exist depending on the implementation. building a decorator is easy given (handles => 'NameOfRole') Package::Variant gives you...