<p>I think my new stance is that all use of [...] is now a code smell. Indexing, slicing, typing, generics, comprehending, whatever. If you see an opening [, you just know that it portends something to follow. </p><p>Actually, I should start referring to [ ] as a &quot;portent.&quot; Instead of saying something like &quot;the expression inside the brackets&quot;, I&#39;d say &quot;the expression inside the portent.&quot;</p>

<p><span class="h-card" translate="no"><a href="https://chaos.social/@Nabla" class="u-url mention">@<span>Nabla</span></a></span> neovim would have to use the CXXRTL protocol <a href="https://cxxrtl.org/protocol.html" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="">cxxrtl.org/protocol.html</span><span class="invisible"></span></a> directly</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> thanks. If I have some time i might give it a look. Or try and glue it to neovim. Thanks in any case for the work. Looking forward to seeing it getting better over time</p>

<p><span class="h-card" translate="no"><a href="https://chaos.social/@Nabla" class="u-url mention">@<span>Nabla</span></a></span> <a href="https://github.com/amaranth-lang/rtl-debugger" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">github.com/amaranth-lang/rtl-d</span><span class="invisible">ebugger</span></a> but it&#39;s very early and it&#39;s not really usable by end users yet</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> is this available anywhere. I really appreciate tooling for this kind of stuff</p>

<p><span class="h-card" translate="no"><a href="https://social.treehouse.systems/@xsk" class="u-url mention">@<span>xsk</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@esden" class="u-url mention">@<span>esden</span></a></span> aw! i&#39;m glad</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> This looks pretty interesting! Like the cadence waveform/source viewer, but in a more modern editor. ✨</p>

<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@AdrianVovk" class="u-url mention">@<span>AdrianVovk</span></a></span> again I&#39;m not seeing the chain of evidence in that commit. If I find something that violates a technical spec, then my commitlog would contain a reference to which specific section of which spec says what. Why not have the same level of commit log quality here? Why are we satisfied with &quot;some undisclosed lawyer gave advice to do this&quot; as follow up to an email thread...</p>

<p><span class="h-card" translate="no"><a href="https://chaos.social/@LaF0rge" class="u-url mention">@<span>LaF0rge</span></a></span> The law makes no distinction between employees of banned companies working on their own time versus on company time. That&#39;s the legal basis of the move.</p><p>And frankly, I wouldn&#39;t want that distinction. The companies on the list are there for a reason: they&#39;re the ones building the tech used to commit the war crimes. The drones and missiles used run Linux. They can, b/c it&#39;s FOSS. But allowing the same people who make the weapons killing Ukrainians participate in our communities is on us.</p>