project-error-handling VS validator

This actually is an example of where the compiler errors could (or should have) maybe provided more help or even the potential solution, it might be worth submitting this to the error handling group.

If anyone's interested in helping to shape the future of Rust's built-in error-handling story, there's an error handling project group that's been doing great work recently, e.g. the major effort to move the Error trait into libcore ( https://github.com/rust-lang/project-error-handling/issues/3 ) and stabilizing std::backtrace. You can follow along or get involved via the #project-error-handling channel on the Rust zulip: https://rust-lang.zulipchat.com/

Getting it into alloc would enable usage in a LOT more contexts, like WASM and kernel code. Does this need a distinct tracking issue outside the ticket for moving it to core or would that just add more administrata?

without trolling https://github.com/rust-lang/project-error-handling exist and is far from having strong conclusion and anyway I will always favor enum Error anyway however I like the idea to have a opaque box in the enum for "this is a opaque error you can't deal with as a user of my api"

IIRC, the Error Handling Project Group is aware of these ideas. If this kind of thing interests you and you want to contribute, you should look into getting involved with that group.

> you should have the underlying message of the std::io::Error

This is a point of debate[1] among the error-handling working group.

[1]: https://github.com/rust-lang/project-error-handling/issues/4...

Focusing on good error messages has permeated throughout the community. There's even the Error Handling Project Group if you weren't convinced how committed the language designers are to getting this right. There are a number of techniques we can use to make our errors more informative. Along the way, we will discuss the crates that can help.

The Error Handling Working Group is looking at potential breaking changes for embedded users. Maybe you could work within that group?

(That's how certain kinds of extensibility work in the validator crate. You just impl a method and validator won't care where it comes from as long as it's in scope because it's built using declarative macros.)

The rust proc macro system is my absolute favorite feature of the language. One of my other favorite libraries is https://github.com/Keats/validator

Hi! I'm happy to announce the release of garde. In summary, this is a rewrite of the validator crate.

Validator : Macros 1.1 custom derive to simplify struct validation inspired by marshmallow and Django validators

https://github.com/Keats/validator needs some help, it's a validation library that easily plugs into Web Development.

(The validate attribute is from the validator crate.)

Would love to use it in https://github.com/Keats/validator when it's ready!

Actually, /u/mehcode just reminded me that this exists: https://github.com/Keats/validator