Whole-known-network
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@shriramk" class="u-url mention">@<span>shriramk</span></a></span> <span class="h-card" translate="no"><a href="https://hachyderm.io/@norootcause" class="u-url mention">@<span>norootcause</span></a></span> jfc good luck</p>
<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@norootcause" class="u-url mention">@<span>norootcause</span></a></span> Went woke, no doubt! Wondering which if any of my grants are on the list. Trying not to pester the provost, I'm sure he has enough email in his inbox tonight. I imagine that tomorrow morning I will wake up to find out that all my current research needs to shut down.</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@dabeaz" class="u-url mention">@<span>dabeaz</span></a></span> as a challenge I understand, but do you expect to get something else out of it? Not trying to discourage. It simply seems like you're cultivating a skill that could have been a lookup in a reference. (Note: I'm not commenting on better comprehension of syntax and language characteristics tho. Those are obviously beneficial.)</p><p>I'm asking from the perspective of cultivating proper logic, reasoning and comprehension, and defaulting to looking up plain facts. (Unless/until cached in brain.)</p>
<p><span class="h-card" translate="no"><a href="https://linuxlab.sh/@palendae" class="u-url mention">@<span>palendae</span></a></span> What I'm really hoping to do is build up my base of "working knowledge" about Rust. Basically, getting a decent foundation of stuff I just know how to do without consulting docs.</p>
<p><span class="h-card" translate="no"><a href="https://linuxlab.sh/@palendae" class="u-url mention">@<span>palendae</span></a></span> Yes. I would not consider myself to be a very strong Rust programmer, but I coded an interpreter in it a few months back. So, in some sense, this was a memory/retention test on myself. If given absolutely nothing, could I create an interpreter again just on my own?</p><p>A lot of it was straightforward. However, there were some fiddly details I couldn't quite recall. So, I had to try some things and rely on compiler error messages to steer me in the right direction.</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@dabeaz" class="u-url mention">@<span>dabeaz</span></a></span> If you’re not consulting docs, are you trying to recall methods via memory/trial and error?</p>
<p><span class="h-card" translate="no"><a href="https://types.pl/@atsuzaki" class="u-url mention">@<span>atsuzaki</span></a></span> <span class="h-card" translate="no"><a href="https://types.pl/@bhaktishh" class="u-url mention">@<span>bhaktishh</span></a></span> <span class="h-card" translate="no"><a href="https://types.pl/@wilbowma" class="u-url mention">@<span>wilbowma</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@jonmsterling" class="u-url mention">@<span>jonmsterling</span></a></span> Unfortunately I think people looking to do PL work at DEC SRC are going to be disappointed.</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@dabeaz" class="u-url mention">@<span>dabeaz</span></a></span></p><p>as_ takes self as a reference, to_ takes ownership of self. Also, there is From trait to convert with ownership transfer and Into trait which is conversion the other way around and Into is automatically implemented for From.</p>
<p>I will say that this exercise, punishing as it is, felt like a great way to try and build an "intuition" around Rust.</p><p>"What the hell was the name of that thing?"</p><p>"from_thing?"</p><p>"to_thing?"</p><p>"as_thing?"</p><p>"Shit!" (much fiddling around with trying different things to follow).</p>