Carl Mäsak

The stackoverflow answer makes the case that anchors were designed to be "point-like", which explains why HTML 4.01 and HTML5 both rule out nested `a` elements. Intuitively, I agree with...

I'm not sure I understand why the first form is erroneous. Where do the plusses come from?

Just going to point out here one consequence of us doing this. (And possibly the biggest reason Perl 6 has gone with "the other" semantics.) sub foo() { class C...

...the problematic thing about `foo().type == foo().type` being `False` is not so much that someone might expect that to be true in their program and be disappointed it isn't, but...

Getting closer to what's actually impossible here: the methods close over the surrounding scope, so they'd have to refresh on surrounding block entry. (So would initializer expressions.) Where do these...

Even if we went with the most restrictive, boringest solution of having classes and their type objects be _very_ static in 007, we'll probably need some kind of "fixup" solution,...

Python sides with Node and makes classes a dynamic thing: $ python3 Python 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] on Linux Type "help", "copyright", "credits" or "license"...

> Getting closer to what's actually impossible here: the methods close over the surrounding scope, so they'd have to refresh on surrounding block entry. (So would initializer expressions.) Where do...

From what I can see, this is how Raku does it: ``` for 1..2 -> $n { class C { method foo() { $n } } say C.WHICH; say C.new.foo;...

Oh right; as was pointed out before. So Raku doesn't really exhibit the co-existence of unique type objects and class closures. D'oh. And maybe it isn't actually possible? When you...