Terts Diepraam

@terts@mastodon.online
146 Followers
154 Following
432 Posts
Software engineer at @nlnetlabs. Co-organiser of RustNL & RustWeek.
Pronounshe/him
Pronunciation/tɛrts ˈdipraːm/
Websitehttps://terts.dev
GitHubhttps://github.com/tertsdiepraam
When writing #Rust code as if it were a high-level language, what is your biggest annoyance/roadblock?
Put another way, what is the biggest thing that gets in the way of Rust feeling like Python or Swift to you?
#RustLang

De Rijksoverheid produceert een tal van podcasts. Vele daarvan zijn helaas niet of nauwelijks vindbaar. Ik vond het tijd om daar verandering in te brengen, en ben begonnen met het maken van een Rijkspodcastregister. De eerste versie staat vandaag online:

https://rijkspodcast.koenvh.nl/

Rijkspodcastregister

De Rijksoverheid produceert een tal van podcasts. Deze website is een overzicht van alle podcasts die de Rijksoverheid heeft geproduceerd.

@algernon Your feedback is absolutely invaluable! Thank you so much!
Thanks to @bal4e for finally forcing me into this and also for the advice to start using jj when your branches are the most messy, because that's when it shines the most!

An unexpected nicety of jj is that you can do many commands without being on the commit that you're changing. With git, I do `git checkout branch`, then do something then `git checkout -` so much, but now it often doesn't matter!

A major downside is all the force pushing, which is much less scary with jj but still doesn't work well with GitHub. But if forges start implementing features around this (e.g. interdiff review), it'll be so good.

Had to rebase a bunch of branches with conflicts and ehhhh... I love jj now.

I could just do all the rebases of all branches and just leave the conflicts. Then go to the conflicting commits and fix them up. No `rebase -i` and editing a text file. No amending, no endless fixup commits. No "rebasing commit 3/15". And when I messed up halfway through, I was able to fix it quite easily.

@algernon Welp, I found at least 4 more issues around constants. I suppose they weren't really covered by my tests. Fixes are in the works!
@algernon Yep, I can confirm that constants need some work. Found at least 1 thing that might lead to that issue: https://github.com/NLnetLabs/roto/issues/203
Constant is dropped when registered · Issue #203 · NLnetLabs/roto

The Runtime::register_constant drops its argument which is supposed to be moved to runtime. This is probably the reason that this issue showed up: https://come-from.mad-scientist.club/@algernon/sta...

GitHub
@algernon If if you are using it wrong then a SIGILL is still really rough. It's been a while since I looked at the constants, so I'll look into that soon!
@algernon Feel free to submit stub issues. I might recognize the limitations or bugs. If I don't recognize it you can always expand on the issue later.
×

The next version of #roto will be packing a really nice mix of new features and quality of life changes! And this is isn't even all of it! Do let us know if you tried Roto and ran into issues!

cc @nlnetlabs

#rustlang