Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
mcmah309’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside mcmah309’s account where mcmah309 opened or reviewed pull requests in the past 365 days.
Who noticed mcmah309
Everyone who starred or forked mcmah309’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories mcmah309 owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
If I understand correctly, this sounds like an issue regardless of using eros or not. You are saying io:Error does not carry all the information you need? In that case, wouldn't wrapping in a container type be enough -- e.g. FileNotFound(io::Error, String) (or even deconstructing the io:Error to whatever shape you want). This is what I would do if I had a recovery tool or message tool up the call stack that could do something based on that type. But if you just want to propagate the information, I wouldn't expose a plain io:Error if it is not actionable, but either way you could just add context .with_context(|| format!("Reading file {file_name}")). Depending on the recipient of this you could use .with_user_context instead. Another alternative is using the #[context] macro. See mcmah309/eros and mcmah309/eros
The source is here. It doesn't use Rust's union, but instead uses a TypeSet which in turn uses some type system magic to turn the set of errors into a compile-time linked list (of up to 26 elements).
Author here. The only downside in my opinion is that is does not work on no_std without alloc. But even this I just figured out with the inspiration of a colleague. Hopefully a PR for this will be up in the coming days -- A lot of pieces to get right and conditional compilation, but the api will be the same. Overall for eros, I meticulously designed the api and am very happy with it. Full flexibility to the developer. Yes there is an anyhow adapter behind the anyhow feature flag mcmah309/eros
やっぱりRustacean皆auto-context的なの欲しいんじゃんってなった スター負けててつらい🫠 mcmah309/eros t.co