People have started looking for 10 alternatives to the now-defunct Actix-web since its death. Some may end up forking Actix-web and evolve it into something uniquely theirs. Others may have started porting their applications to other frameworks or even out of Rust. Continue Reading
Have you started using Actix-Web in your learning of Rust or real projects? Actix-web is now dead and no longer an open-source project. The author has moved it, along with Actix-Net, to his personal GitHub account. He is taking his… Continue Reading
Macros are like functions but only better. They are triggered based on their patterns using pattern matching for declarative Macros. They group together our codes into a unit (or units) and there are 2 types of macros in Rust – declarative and procedural. This brief post is about declarative macros. Continue Reading
At some point in learning Rust, we will encounter the need to create our own crates. They need to go through development and testing before there are published to creates.io. This brief post is about creating and using local unpublished crates. Continue Reading
Non-exhaustive structs will future-proof our codes. We use Struct expressions to instantiate structs and they’re JSON-like expression in appearance with all fields present. When we update a struct with a new field, all expressions must be updated to include that field. Continue Reading
Using non-exhaustive enums in one crate prevents codes in other crates from listing all the possible matches in a match expression. It forces developers to use wildcards for future-proofing. Continue Reading
In Rust, we can read user inputs from the command-line console. These inputs are string values with newline characters at the end. Most of the time we do not want those extra characters. This post provides 3 basic example codes… Continue Reading
Anything has a state. An entity has a state. Similarly, a car can be in a state of acceleration. While it is accelerating, there are some things it certainly cannot or should not do, e.g., reversing at that very moment. The State Design Pattern treats each state as a struct whose functions represent movements to the other states. Continue Reading
This Design Pattern uses commands to wrap and invoke capabilities. A car can run faster and slower. We can have commands AccelerateCommand and DecelerateCommand for increasing and decreasing speed, respectively. We can also have AccelerateAndDecelerateCommand to run both capabilities in a certain order. Continue Reading
This Design Pattern replaces a behavior with different implementation at run-time or sometimes at load-time by means of configuration. Two entities could have different implementations of the same behavior. Continue Reading
