Darren Duncan

Generally speaking I strongly dislike any solution that uses some kind of special value to stand in for a missing element, as the rest of this thread has discussed. I...

> ``` > @repr = deconstruct_object $obj; > $obj = construct_object @repr; > ``` > > I like that. I feel that it would be best to be more descriptive,...

> As it happens, with https://github.com/muldis/Muldis_Object_Notation/blob/master/spec/Muldis_Object_Notation.md I am in the process of formally defining a format, "Muldis Object Notation Syntax Perl", which is expressly designed for the use case you...

> There's also [the question of what `ref` and `Scalar::Util::reftype` will return](https://github.com/Ovid/Cor/issues/5#issuecomment-784036797). The most important thing is that these routines will return some new value that is unique to Corinna...

To go along with Corinna, Perl should globally (such as provided in `UNIVERSAL` provide a routine/operator/method with a name like `as_preview_string` or (nee `as_debug_string` or `as_debug_dump`) etc, pick a name,...

On a tangent, with my own Muldis Data Language / Muldis Object Notation project, I have designed it such that implementations explicitly have 3 distinct methods for serializing values as...

> Sounds like Str and Gist in Raku to me and yes I love those! Yes, that's along the lines of what I had in mind. In particular Raku's gist()...

@wchristian said: > > Between its name and that, developers are NOT to count on being able to parse and use it programmatically in any reliable way > > Let...

> I came here because Ovid closed #30 and pointed at this issue. Your post seemed to be the only one with anything similar to a solution to the larger...

> I am not married to any one particular solution*, and am currently only advocating for the premises to be determined, but that sounds reasonable, yes. > > * for...