Oh what shall I put here?
I really don’t know.
The has it all, I fear—
And there’s little else to show.
Still, if you’re curious, there’s more about me…
Recent blog posts
Rust ownership, the hard way
In order to truly understand Rust, one needs to understand its crucial differentiating feature: ownership. Let’s go through it in detail the hard way.
Quick tip: the
#[cfg_attr]attribute is a really handy way of reducing code duplication in some situations.
Why your first FizzBuzz implementation may not work: an exploration into some initially surprising but great parts of Rust (though you still might not like them)
FizzBuzz is intended as a simple task, but in Rust there are a few pitfalls for the novice to be aware of. These aren’t problems with Rust but rather differences from what people are commonly familiar with, restrictions that may seem arduous at first but ultimately give you more power, at a small cost.
Teepee design: the HTTP method
Now we come to the
Methodtype. While there are a few improvements to be made, this is one of the things that probably can’t be significantly improved on over rust-http.
Teepee design: header representation
Header representation is a critical matter to Teepee’s design: it is uncompromisingly strongly typed, but there must be tradeoffs. After trying quite a few different schemes at length, I have settled upon quite a novel scheme which I believe to optimally balance all considerations.
Status-Line, take two
Teepee design: a careful look at the HTTP/1.1
rust-http has a nice
Statusenum which provides good, strong typing of statuses, but alas, it is not without its issues. Let’s take a look at the
Status-Lineas it is defined.
- See more blog posts…