Carl Mäsak

Rethinking the MOP and the names a little, I think this is what I want: - `Type` - `T::Class` - `T::Tuple` - `T::Enum` I'm already going with the `class` and...

There's a total collision between subcalls `foo(1, 2, 3)` and tuple creation syntax `MyTuple (1, 2, 3)`. (That space there is just convention. It's good for humans, but 007 ignores...

> - As a consequence, there's no private state. You can't even emulate it by having the methods close over a lexical defined outside of the class. (Or you _could_,...

> -1 to changing `my`'s behavior in class as compared to Perl 6, I'd argue either it's lexical or it's not. It _is_ lexical. What's changed isn't the behavior of...

> The other solution would be executable class bodies, scala-ish variant where everything in the class body is ran in order We kinda have this, except that we're conservatively restricting...

I think it would be nice to start implementation of this feature pre-v1.0. I suggest we try doing it behind a feature flag (rather than a branch). I don't want...

At first glance, I'm surprised to see an unquote outside of a quasi. But I guess that's an Elixir thing?

I see. Though I'm unsure what you're suggesting here for 007. Would you like the `class` block to be an implicit `quasi` block, so that unquotes work inside of it?...

Ah, I see. Yes, that discussion is very much worth having. Thank you for bringing it up. I have no idea how the balance will come out between macros/Q and...

Thinking about this, I realize what we do need a good story for is how to inline a bunch of stuff (attributes and methods) into a class using unquotes and...