New week, new Rust! What are you folks up to?
asfd, a tool to automatically validate checksums of files downloaded with it (eg from Github Releases).
1 Like
(closed source ¯_(ツ)_/¯ ) embedded device programming. Learning async and using embassy has been a treat since my prior experience has been on std rust in embedded linux with preemption as the timesharing model.
Last week I released version 0.2.0 of my library exhaust. It lets you iterate over all possible values of a type — and unlike other libraries that do similar things to fieldless enums only, it works on nested enums, structs, and standard library types too. It's useful for building maps which are guaranteed to contain all keys, exhaustive testing of cases, and solving problems by brute force search.
The big feature in this version is that it no longer requires types to implement Clone. This means that, for example, it can construct types that contain Mutex or atomics, or that are in any other way made from plain data but don't act that way after they are constructed.
I'm also thinking about adding an indexable form, allowing converting between any data implementing the trait and a number (that could be an index into an array acting as a map, for example); take a look at issue #20 if you’d like to review the plan.
4 Likes
Nothing exciting.
I started learning rust about a month ago. What I'm at is an XML parser (in a working state right now). I implemented one in C several years ago. It is less than 600 lines, including comments. Then, about 2 years ago, I decided to learn a new language. It was OCaml. I took a break of about a year and re-implemented that XML parser in OCaml. About the same length. Then, one morning I got up and continued coding and asked myself "Why continue using this odd language?". Next day, I started with rust and still feel good about the decission to switch. 900 lines mostly because of formatting-bloat. But better code and more robust.
That XML parser is just part of an idea I had years ago. A software for designing cam-shafts of internal combustion engines that are restricted by mechanical constrains. So not the classical way of defining a lobe and then discover that the contact pressure is to high.
Side product (planned) is generating C-code for a cylindrical CNC-grinder. I had a similar software written in Tcl/Tk for milling cam-shafts.
Well I don't know what will be the result, but it will be a good opportunity to learn rust with a real application. But just a side project in spare-time.
1 Like
I am working on a parser generator. Today i got it compiling again after changing a lot of stuff. Now i have to work on documentation and tests a bit before i will add more features. Longterm plan is to create random programming languages with it. HenriksParsingProject. Would love some feedback or construcive criticism.
I'm writing a gRPC server for Xvc this week. It allows to manage large data and ML pipelines on servers and VMs.
It's very early prototyping stages, but I'm looking into the viability of doing quasi-quoting (ala syn) but with ahead-of-time (i.e. when the caller compiles rather than when it runs) validation that the quoted code fragments are syntatically valid
I'm working on making the analyzer of bacon more modulable and easier to test, so that it can be used for example with nextest, or even more exotic tools.
First step was an export function & shortcut to grab the last analysis.
1 Like
Brainstorming Ideas for Hackathon
I’m trying to brainstorm ideas for my college hackathon. I recently finished reading the Rust book, but I’m struggling to think of any good projects that I could build using Rust for the open track or any other hackathon tracks.
There's a newer installment of this weekly discussion here: What’s everyone working on this week (42/2024)?.
However, an even better place to post this request would be to initiate a + New Topic in the help category. Your request is likely to get more attention there.
2 Likes
Thanks for the advice
1 Like