Whole-known-network
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> I want a theme for my IDE called "Metal!" where this guy sings all of the auto-complete suggestions to me. 🤘</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@film_girl" class="u-url mention">@<span>film_girl</span></a></span> OMG, what a day! I'm going to go shop for passport wallets with AirTag holders while drinking wine because this is something that would happen to me.</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://techpolicy.social/@joebeone" class="u-url mention">@<span>joebeone</span></a></span> seen this?</p>
<p><span class="h-card" translate="no"><a href="https://functional.cafe/@PaniczGodek" class="u-url mention">@<span>PaniczGodek</span></a></span> Ah, yes, you are right. But I view metacircular interpreters as different.</p><p>There, the idea is to reduce the problem down to its essence; often, implicitly or explicitly, the goal is to fit everything in as little space as possible (eg, Kay's comment about McCarthy's interpreter). Then you indeed want to avoid unnecessary phases.</p><p>But if you're trying to write a *production* interpreter, rather than an illustrative one, then you'd want to have a parser.</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> Nanowar on fuckin point as usual</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> This is great!</p>
<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@smurthys" class="u-url mention">@<span>smurthys</span></a></span> Oh, cool! Meier is great! I believe Stan and Dave worked together a lot in the halcyon days of OODBs.</p>
<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@adamshostack" class="u-url mention">@<span>adamshostack</span></a></span> Sssh, we do not speak of these things on non-covert channels!</p>
<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@jschuster" class="u-url mention">@<span>jschuster</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@mudri" class="u-url mention">@<span>mudri</span></a></span> <br />This is a very reasonable question. It is hard to answer because there isn't a canonical answer for what the output of the parser is.</p><p>For instance, a typical parser does not type-check (which is clearly context-sensitive). But not everything may be context-free. E.g.: the AST may not just have "names", but may have bound instances referring to binding locations. If so, the parser needs to keep track of them as it goes along, which is context-sensitive.</p><p>Make sense?</p>