On Jun 4, 2019, at 4:22 PM, Brian Goetz wrote:
>
> For prototyping purposes, I wouldn't try to use the same token; that's just
> making your life harder. Pick something easily parsable, even if its hideous.
In fact, it's often beneficial to adopt a __ClearlyHideousSyntax for
prototyping or
Alan;
Thanks for these thoughts. Indeed, field references are something that
keep coming up in the "if we only had" department, and your analysis
covers many of the important points. They are especially useful in APIs
such as the Equivalence one that Kevin and Liam have already written
- Mail original -
> De: "Alan Malloy"
> À: "amber-spec-experts"
> Envoyé: Mardi 4 Juin 2019 00:19:10
> Objet: Revisiting field references
Hi Alan,
i'm sorry but i've more questions than answers,
> Hello, amber-spec-experts. I understand that "field references" is an
> idea that was
