I recently got frustrated by the changeset CLI - as far as I know, there is no option to create changesets that are not empty without using the annoying prompt and arrows to select patch/minor/major. And I don't have arrows in my small keyboard ;)
Let's fix it - without leaving Emacs.
When I code, I sometimes move from a place to another - where light condition is not the same. Usually, I would either adapt to these changed condition passively, or aggressively switch from dark to light mode, for instance.
Let's dive into the solution I'm using!
Recently, I saw a post on r/rust about creating a macro to check the execution time of a
specific function - and my brain just went DECORATOR so... Let's try to build a small
proc_macro, shall we?
I've been wondering how hard would it be to write a data packer. And since Rust is my language for experimenting these things... Here we are! This short entry is about the few things I've experimented with when writing Easypack, my new toy.
I've been doing Rust for fun for at least a couple of years now, and I've
almost never had to use the unsafe keyword. I think it is time to address
this lack, and what is a better case-study than implementing an heap based stack? ;)
During the last Hackathon, we were asked to do some challenges, just for fun. One of them forced us to hack a small binary to get an address and use tcpdump to get a password.
How the hell am I supposed to do?