Paul Evans

@Ovid Quick reminder that `reftype` isn't `ref`. `reftype` gives you a string that's one of a few standard fixed ones, to name the basic container type of a referrent. `ref`...

@Ovid > Why would we need `construct_object`? Is this for freezing/thawing? Yeah, basically just for weird cases like Storable, Sereal, etc... It probably shouldn't be used much besides those. Though...

@Ovid > [As metioned here](https://github.com/Ovid/Cor/issues/62#issuecomment-1176315897), I would much prefer if `deconstruct_object` either mark the data read-only or clone it (or COW) A useful-sounding idea, but a bit tricky to arrange...

> I don't see a keyword named 'attribute' there. ``` class Ball :isa(Toy) :does(Roundness) { ... } ``` ^-- `:isa` and `:does` are attributes. ``` field $size :reader :writer :param;...

It would be very very confusing to have two totally-distinct concepts, both called "attributes". Especially if these object fields can have attributes themselves. How would you distinguish ``` attribute $name...

Latest thoughts: While it doesn't help the field-initialiser block, an `ADJUST` block could still work with something that happens superficially to look like a signature. The same parser hackery that...

Thinking further about it, I'm not sure I like the exact syntax of this latter approach. It's nice to imagine giving an `ADJUST` block a way to request the name...

And now some more examples on the "declared metadata" front... Looking around at various actual `ADJUSTPARAMS` blocks I have in real code right now, it seems most of them operate...

Your suggestion there doesn't seem to any clearer answer how to handle these different params. Perhaps a concrete example is needed. Lets imagine some UI widget that needs a title...

> The issue with your code example is that the "fields" `$red`, `$green`and `$blue` are just waste after the construction of the object, but can't be disposed of. This is...