0 Dependency Error Crate

1

Hi everyone (this is copied from reddit)!!!

I've been developing a 0 dependency error crate with an API similar to anyhow for a while now!! It is designed with a friendly API first for frontend applications/small backend API's.

It similarly allows for the try operator on most error types, with a Result< T >, BoxResl< T >
Sorry I didn't include this before. Wasn't super ready to post it yet, and was really seeing if there was interest!

//An example of using the API


fn example<T>(any:T)->Result<T>{
mostresultfunc?;
anyresultfunc.map_appair()?;

//Add context to errors with an API similar to anyhow
anyresultfunc.with_context("msg")?;
anyresultfunc.any_context(d:Display)?;

//Assign error codes 
anyresultfunc.assign_code(f64)?;

//Minimal example of a new error
AppError::Error("static error msg")
AppError::from(error string)
}


///Under the hood this uses dynamic errors and can be
///Used concurrently with Result<T>
fn example<T>(any:T)->BoxResl<T>{
anyresultfunc?;
anyresultfunc.map_appair()?;
anyresultfunc.with_context("msg")?;
anyresultfunc.any_context(d:Display)?;

//Creating a new error
BoxErr::new()
}

It is somewhat performant, though it does especially well in frontend apps (especially Tauri/Flutter Rust Bridge). If there is any interest let me know, and I will make it public, otherwise I'll just keep this implementation personal​:face_savoring_food:

2

What's the purpouse of announcing something that is not public? It Is pretty difficult to decide if some crate will be usedul to me without docs and, in some case, source code.

3

The point is I am seeing if there is any interest/if it's worth it for me to release publicly. I probably will just keep this one to myself, for the time being, until it has enough features to drum up more than 1 semi-interested comment. I do admit I should explain/market it better, and will keep that in mind!!

4

Insofar there is interest in this, it'd be to play around with it in order to evaluate it.

But since the project is not publicly available, that prevents such evaluation from the get-go.

5

Thank you for saying that, people have correctly pointed out elsewhere I need some polishing up of read me's, etc (to be fair I wasn't quite ready). I guess I don't know what I wanted. I'll probably end up releasing by the end of the month!!

6

Publishing a WIP git repo or similar would be a good thing to go with the original post - no need for it to be ready to publish to crates.io, no need for README.md and similar to be in good shape, just something where I can look at the code and compare to anyhow to see if I want to help you get it to publishable state.