<p><span class="h-card" translate="no"><a href="https://mastodon.online/@danirabbit" class="u-url mention">@<span>danirabbit</span></a></span> 🥳 Just getting into your prime. Happy birthday! 🎂</p>

<p>I wrote my first “real world” <a href="https://types.pl/tags/ATS" class="mention hashtag" rel="tag">#<span>ATS</span></a> application that does something for me. It was wild wrangling the errors, especially when dependent, refinement, &amp; linear types were involved since I have no experience with them, but eventually it all actually managed to click.</p><p><a href="https://hub.darcs.net/toastal/svg-sprite-plucker" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">hub.darcs.net/toastal/svg-spri</span><span class="invisible">te-plucker</span></a></p><p>Honestly, not half bad to write. +1 for having a low-level ML.</p><p>If I could fix anything with the language it would be:</p><p>1. Don’t be limited to 128-char ASCII which could really open up operators to have less overloading + accessibility for non-English speakers<br />2. Unicode string support (being worked on)<br />3. Better type errors; the data is there, it’s just really noisy with with wrapped elements for type-level errors &amp; showing the diff of mismatched types is often more useful than the whole info<br />4. Record update &amp; punning syntax</p><p>&amp; language ecosystem, it would be:</p><p>1. a glossary of the keywords to help understand them at a high level<br />2. better FFI explanation since one of the powers is very close C interop; bonus for mappings of zero-cost ML abstractions to the ones in C libraries (instead of me having to trudge my way thru it via guess &amp; check)<br />3. better explanation of how the build system works *outside* of `patscc`<br />3. tree-sitter parser<br />4. language server protocol LSP</p>

<p>I wrote my first “real world” <a href="https://types.pl/tags/ATS" class="mention hashtag" rel="tag">#<span>ATS</span></a> application that does something for me. It was wild wrangling the errors, especially when dependent, refinement, &amp; linear types were involved since I have no experience with them, but eventually it all actually managed to click.</p><p><a href="https://hub.darcs.net/toastal/svg-sprite-plucker" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">hub.darcs.net/toastal/svg-spri</span><span class="invisible">te-plucker</span></a></p><p>Honestly, not half bad to write. +1 for having a low-level ML.</p><p>If I could fix anything with the language it would be:</p><p>1. Don’t be limited to 128-char ASCII which could really open up operators to have less overloading + accessibility for non-English speakers<br />2. Unicode string support (being worked on)<br />3. Better type errors; the data is there, it’s just really noisy with with wrapped elements for type-level errors &amp; showing the diff of mismatched types is often more useful than the whole info<br />4. Record update &amp; punning syntax</p><p>&amp; language ecosystem, it would be:</p><p>1. a glossary of the keywords to help understand them at a high level<br />2. better FFI explanation since one of the powers is very close C interop<br />3. better explanation of how the build system works *outside* of `patscc`<br />3. tree-sitter parser<br />4. language server protocol LSP</p>

there was a piano concert in my research center today, someone played some yoasobi :cirno_think:

<p>&quot;We&#39;re not weirdos,&quot; say the members of a fascist pedophilia cult led by Jeffrey Epstein&#39;s best friend of 15 years who is running for President on a platform of having the government inspect teenage girls&#39; genitals and monitor their periods.</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://pubsub.leastfixedpoint.com/@tonyg" class="u-url mention">@<span>tonyg</span></a></span> The precedence in C caught enough of my students off-guard that I now have my TAs walk through an example to demonstrate clearly which is evaluated first: comparisons or bitwise operations.</p>

@rin@post.ebin.club wtf even this cd got government original qrcode sticker

<p><span class="h-card" translate="no"><a href="https://functional.cafe/@loke" class="u-url mention">@<span>loke</span></a></span> no, of course it isn&#39;t!</p>

<p><span class="h-card" translate="no"><a href="https://pubsub.leastfixedpoint.com/@tonyg" class="u-url mention">@<span>tonyg</span></a></span> haha T__T</p><p>tbf the bitwise operation precedences make more sense than in c, but also that it&#39;s different than in c is an issue in its own right... and then people get clever with it</p>