competitive-programming-rs VS sniper

I have this question because, as practice, I'm trying to implement a struct Scanner based on this repo, and as an extra, I'd like to be able to handle errors instead of just panicking. However, unlike map(), the skip_while() and take_while() won't handle errors. If the Errs wouldn't happen unless in situations when the program were going very wrong, then I could just panic. Alternatively, is there a way to break and just return an error once bytes() gives an Err, with just iterator function chaining and without having to write loops myself?

This week I read about FnMut and FnOnce. I also found some amazing Rust code for parsing input/output for competitive programming , and solved all the google kickstart problems using it. I made two one hour video of my efforts starting here: https://youtu.be/EvL5YfPw8Ts

It's a snippet manager that uses a client server approach to handle modular (eventually programmatic) snippets. the communication happens between client and server via Grpc. The goal of the project is to make all the work happen server side, or at least enough that implementing extensions for other editors would be trivial (so long as those editors have a way of storing persistent state)

So, I'm really loving rust, something about compiler time guarantees alleviates some perfectionist tendencies that do more harm than good in other languages, I tend to take more risk or worry less about making mistakes. it also really helps that the community is all about "defacto-standards", there are generally one or two heavily documented ways of handling things (compared to javascript where there are like 7 different libraries for handling requests, or concurrency in c++), which makes it easier to learn. I recently attempted a major project where I code almost everyday for 2 months out of enjoyment, built something that while still has a while to go before reaching mvp status, is pretty cool and really pushed my understanding of things in a major way.