Comments (4)
I hate to be the necromancer, but... Will this ever be implemented?
from derive-error-chain.
Not by me.
-
error-chain
itself has been abandoned (again). -
Most new users don't know
derive-error-chain
exists, so they compareerror-chain
withfailure
and go withfailure
(and rightly so). -
derive-error-chain
has a disadvantage with respect to needing to keep thebacktrace
attr in sync witherror-chain
'sbacktrace
feature, which causes all sorts of problems.failure
's design of requiring explicit backtraces or usingContext
doesn't have that problem, which is why at least one of the original users ofderive-error-chain
moved to it. -
Even for my own projects, I've dropped
derive-error-chain
for manual enums orfailure
.
So I don't really care to continue working on this any more. If someone makes a PR I'll be happy to merge it.
from derive-error-chain.
I see. Thanks for your reply!
This will probably be off topic, but given the flux in the error-handling ecosystem right now, which crate would you recommend using, if any? I understand that failure
mostly exists to experiment, and might not exist in the future too. I used to think that error-chain was the way to go, but now there isn't any one crate that looks like a clear default.
from derive-error-chain.
failure
is fine for now.
from derive-error-chain.
Related Issues (20)
- Port error-chain's tests
- Support specifying custom `Error::cause`
- Replace `error_chain!` HOT 6
- Make Sync configurable
- Future alias? HOT 1
- Make Msg optional
- Rename `#[derive(error_chain)]` to `#[derive(ErrorChain)]`
- Don't require `ErrorKind` to be `pub`
- Update pm2, syn, quote for nightly breakages
- Switch to new proc_macro_derive
- Undocumented dependencies HOT 4
- Support deriving on structs
- Allow backtrace to be optional
- Update example and tests for #[cfg] on variants
- Use upstream traits - Backtrace, ChainedError, ErrorChainIter, ResultExt, State HOT 18
- Add `const("some string literal")` as a shorthand for `description()` HOT 2
- Add `const("some string literal with {parameters}")` as a shorthand for `display()` HOT 4
- Change display and description to receive all members instead of a tuple of the members
- Documentation updates
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from derive-error-chain.