rust-phf VS patterns

could you create compile-time maps with https://github.com/rust-phf/rust-phf ? that way you don't pay the performance penalty of reading the ron files at runtime

However I'm still stuck for the matching between packet and handler. Phf map (static maps) doesn't support mapping to enum so I have to make a matching clause :

Have you seen the crate phf?

Maybe phf will come handy?

This is sort of an aside, but turning a not small index into a match statement is probably going to use more memory than the base data and suck for compile time. Might be smarter to include the index as bytes for ex with include! and interpret it directly. You could precompile a hash table with something like rust-phf: https://github.com/rust-phf/rust-phf.

A great example of how this is typically done is the phf crate: https://github.com/rust-phf/rust-phf

https://github.com/rust-phf/rust-phf comes to mind.

If you’re looking for something like gperf: https://github.com/rust-phf/rust-phf

Are all the keys known at compile-time? If so https://github.com/rust-phf/rust-phf might be best.

For OOP design patterns in Rust, see: https://rust-unofficial.github.io/patterns/

For a book on FP, see: https://www.manning.com/books/grokking-simplicity

Just wanting to let this here for some further input: - https://rust-lang.github.io/api-guidelines/ - https://rust-unofficial.github.io/patterns/ - https://deterministic.space/elegant-apis-in-rust.html

Rust Design Patterns

I know about Rust Design Pattern what are your reviews for the same?

Once you've finished with The Book and possibly Programming Rust, 2nd Edition if you've got the cash for a paid book, read Learning Rust With Entirely Too Many Linked Lists (it helps to solidify what ownership and borrowing mean for data structures) and Rust Design Patterns.

Well, there's https://rust-unofficial.github.io/patterns/ for a start.

Love the translation pipeline, currently looking into adopting that as well for the Rust patterns book!