const_irc_message_parser
| Crates.io | const_irc_message_parser |
| lib.rs | const_irc_message_parser |
| version | 0.9.0 |
| source | src |
| created_at | 2023-08-20 14:38:54.181513 |
| updated_at | 2024-09-24 20:36:53.506255 |
| description | A 0 dependency, no_std, const-only parser for the IRC message protocol. |
| homepage | https://github.com/auronandace/const_irc_message_parser |
| repository | https://github.com/auronandace/const_irc_message_parser |
| max_upload_size | |
| id | 949404 |
| size | 157,449 |
(auronandace)
documentation
https://docs.rs/const_irc_message_parser
README
const_irc_message_parser
A 0 dependency, no_std, const-only parser for the IRC message protocol.
Motivation
I wanted to see how much of an IRC message parser can be written in a const context. Every public and private function is const. I was even able to make all the tests const functions even though it ends up being more verbose. The only exceptions are the Display impls as functions on Traits are not yet allowed to be const (https://github.com/rust-lang/rust/issues/103265). I am also unaware of how to test Display impls in a const manner for code coverage. Suggestions welcome.
Documentation
Documentation can be found here: https://docs.rs/const_irc_message_parser
Acknowledgements
- IRC Message specifications: https://modern.ircdocs.horse
- IRC Message Tags specifications: https://ircv3.net/specs/extensions/message-tags.html
- IRC Formatting specifications: https://modern.ircdocs.horse/formatting