rust

Today I published my first rust crate.

Recently I decided that I might actually publish my little rust crate. To that end I started looking into some of the things that are needed and what can be done. I have published a perl module in the past. And as a rule for myself, I like to provide an example program that uses a module or library. That is what I will look at today.

Hi,

Today I will finally go over how I used the lazy_static crate to help the compiler keep regex optimised.

Recently, as I work my way through learning bits of rust, I have been thinking that I should in corporate some form of input validation for domains.

Today I will look at two crates.

In the previous article in this series I went through some basics of documenting your rust code. I had hoped to be able to take advantage of another nice feature of rust. That being the fact that code examples are actually tested by rust. I will go through the changes I had to make for this to work.

Hi.
As with all projects. It’s important to create documentation. This is, as we know, very important when creating code. When we come back to a project after a break, or if someone new takes over. Documentation will help you remember or learn what the code does. The thinking that was behind certain decisions.

This is a quick followup on my progress in deconstructing SPF using Rust.
Today I was able to implement both A and MX mechanisms.

Hi. In my previous article Looking at Regex in Rust. I covered some basics. Today I will go over some new things that I have learned, as I expanded on things that my regex expression needs to handle. In particular the need to handle the possible existence or none existence of qualifiers +,-,~,?.