oSUS VS object-provider

oSUS - osu! utilities in Rust. I use it for instance to convert a map from lazer to stable format, as well as to hitsound beatmaps more efficiently (I like doing that)... I have an osu! mapper friend who keeps filling my hitsounding queue with his beatmaps xD

Not a crate yet, but here's my oSUS project.

I've been slowly rewriting my osu! file parser to use nom and miette for top-notch error handling. I used the same small error handling architecture as the KDL project for that and I think I can pull it off eventually. https://github.com/Speykious/oSUS

Here's the project

Yup! This is kinda how I got sucked down the rabbit hole of error handling, I wanted to be able to use https://docs.rs/tracing-error/latest/tracing_error/struct.SpanTrace.html instead of Backtrace but it was impossible to pass arbitrary contexts out of dyn Errors, and there was zero chance in hell that I was gonna get SpanTrace added to std, so I had to get creative. My original idea was to just pass in a type id and get a dyn Any back out but luckily my friend nika had better ideas and helped design https://github.com/mystor/object-provider/ and eventually https://github.com/mystor/dyno/, which then eventually was used as the basis of nrc's Provider RFC. A team effort really but I definitely view it as my baby because the error handling use case was the root motivation of it all.