2
<p><span class="h-card" translate="no"><a href="https://mas.to/@brena" class="u-url mention">@<span>brena</span></a></span> love this shot!</p>
<p>After literally 7 years of attempts and at least 3 purchases, my dad is finally giving AirPods Pro a proper try thanks to the hearing aid feature. My mother currently cycles between 3 pairs of AirPods and is about to buy a second pair of AirPods Pro 2s but dad has been resistant. I’m so relieved.</p>
<p><span class="h-card" translate="no"><a href="https://wandering.shop/@rezendi" class="u-url mention">@<span>rezendi</span></a></span> Yeah, I think this is really it.</p>
<p><span class="h-card" translate="no"><a href="https://aus.social/@robs" class="u-url mention">@<span>robs</span></a></span> It&#39;s not like a verified compiler, it&#39;s like translation validation (-:.</p>
<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@allafarce" class="u-url mention">@<span>allafarce</span></a></span> I&#39;ve come to realize that it&#39;s not actually a technical remark, it&#39;s actually a political one. Basically it&#39;s a statement of tribal identity (especially when preceded by &quot;just&quot;).</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.nu/@richcarl" class="u-url mention">@<span>richcarl</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@DRMacIver" class="u-url mention">@<span>DRMacIver</span></a></span> <br />I don&#39;t think auto*complete* is much more useful. Prompts like mine involve *quantification*: on *every* round, do X. It doesn&#39;t just do X; faithfully executes for-all X (for several rounds anyway). I don&#39;t know any &quot;autocomplete&quot; that behaves like that.</p>
<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@dlharmon" class="u-url mention">@<span>dlharmon</span></a></span> I suppose more accurately what I want to build would be described as &quot;timing check during synthesis&quot;</p><p>rather than merely considering CDCs it uses a more abstract model than P&amp;R to conservatively avoid violations</p>
<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention">@<span>0xabad1dea</span></a></span> suffering</p>
<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@dlharmon" class="u-url mention">@<span>dlharmon</span></a></span> sure they would, all toplevel inputs would be considered asynchronous to any clock in the design unless marked otherwise</p>