Carl Mäsak

A couple of things about the use cases: * I'm intrigued by the idea, and willing to try it out. * As a concrete suggestion, @raiph how about we set...

I was going to drop in here and say that it fits nicely with the things later described in #410. But then I looked at the example and had to...

> And that should be enough to throw the needed exception. Should it, really? Isn't the "can't see the original declaration" criterion the one we wanted to use for regular...

> > And that should be enough to throw the needed exception. > > Should it, really? Isn't the "can't see the original declaration" criterion the one we wanted to...

...the rationale for this difference in treatment being that (b)-style code "knows what it's doing" playing with fire^Wdetached lexical lookups, whereas (c)-style code is by its definition hapless, acted-upon, and...

I think this one would be great to tackle, because it would shake out relatively common patterns of dealing with code. Though linting and refactoring are still distinct from the...

Though it's not a blocker by any means, it's intriguing to think that after we have #38, we might write this tool in 007 as well. That's not to say...

oh, and a ## code tidy-fier Like [Perl::Tidy](https://metacpan.org/pod/distribution/Perl-Tidy/lib/Perl/Tidy.pod) or [gofmt](https://golang.org/cmd/gofmt/). ``` spy --tidy script.007 ```

> Though it's not a blocker by any means, it's intriguing to think that after we have #38, we might write this tool in 007 as well. That's not to...

> - Variable read from before being assigned to I wanted to say that the "before" here is interesting. It's not "source order", it's execution order. #160 is a good...