fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

#rust

285 posts229 participants29 posts today

Me, 6 months ago: Let's Rewrite It In Rust! I could write tooling to migrate the build from a blob of mud to a DAG, but that sounds like too much up front. I bet I can make all these changes by hand...
Me, 2 months ago: Sigh, that didn't go so well. Let's try again, using a different approach for the refactor...
Me, last week: Sigh, that's not working out, either! Guess we should roll some tooling after all. Let's start simple...
Me, this week: ...aaand I'm basically implementing a linker

Damn. I thought #Zig was supposed to be a simpler language coming from #Rust but compiler errors definitely aren't it's strong suit.

This is one of the first impressions I got from the language. I'm just trying to compare some strings here, nothing magical. But apparently this is not an easy task in Zig. The documentation is definitely lacking examples too.
Also it's missing a good beginner introduction like the Rust Book.

The code in question: bpa.st/3VYA

Replied in thread

@KingmaYpe @drgroftehauge I'm not feeding this version to Clippy. We've not met and likely won't for a while yet. ;-).

I'm at the "got all the moving parts out of my head and doing their various movings on actual machines finally" phase, and just grateful to have gotten there.

I started learning #Rust probably five or six weeks ago for this project and I know my stuff isn't up to Clippy's criticism - or standards.

Replied in thread

@KingmaYpe @drgroftehauge

That works well since I'm sure my existing code is *ugly*. I don't actually *think* in #Rust yet. Rust iterators and filters are still alien tools to me, so what I'm writing is really kinda a bastardized C with struct methods that follows ownership rules. A lot is, I'm sure, a lot longer and more dogmatic/pedantic than it should be if I were using the language properly.

Hopefully I'll be writing rustier Rust by the time I start component by component rewrites.