Comments (6)
benaryorg
commented on June 3, 2024
I don't know what's happening here, but I am using error-chain on stable Rust and it seemed to work flawlessly.
from error-chain.
benaryorg
commented on June 3, 2024
I just checked and error-chain builds (and works) with that:
cargo 0.11.0-nightly (259324c 2016-05-20)
rustc 1.10.0 (cfcb716cf 2016-07-03)
Output of cargo:
Compiling error-chain v0.2.2
Running `rustc /home/benaryorg/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.2.2/src/lib.rs --crate-name error_chain --crate-type lib -g -C metadata=08db5cd4c8eb6242 -C extra-filename=-08db5cd4c8eb6242 --out-dir /home/benaryorg/Documents/project/target/debug/deps --emit=dep-info,link -L dependency=/home/benaryorg/Documents/project/target/debug/deps -L dependency=/home/benaryorg/Documents/project/target/debug/deps --extern backtrace=/home/benaryorg/Documents/project/target/debug/deps/libbacktrace-dffaf784d6265843.rlib --cap-lints allow`
(only relevant output displayed)
from error-chain.
brson
commented on June 3, 2024
Oh, nice. Thanks for testing @benaryorg.
from error-chain.
benaryorg
commented on June 3, 2024
Also, I've retested with version 0.2.2 and still the same result, a seamless build without any error/mistake.
Edit: Original response updated
from error-chain.
birkenfeld
commented on June 3, 2024
The problem is with using error_chain inside a function, as in the smoke tests.
It is "easily" (once you figure it out) fixed by appending a semicolon. PR incoming.
from error-chain.
brson
commented on June 3, 2024
Thanks @birkenfeld !
from error-chain.
Related Issues (20)
- If this crate is really drepecate, I should specify it and mark alternatives. HOT 8
- cargo publish error HOT 3
- deprecate quick_main?
- trait objects without an explicit `dyn` are deprecated
- changes to backtrace crate HOT 1
- Shouldn't src/bin/has_backtrace.rs be in examples? HOT 1
- How to implement complex display expression?
- backtrace name collision HOT 1
- use of deprecated try
- minimum version 1.13 for ? operator HOT 1
- How to force documentation when using error_chain HOT 5
- Move Repository To rust-lang
- lint error: use of deprecated item 'std::error::Error::description': use the Display impl or to_string() HOT 2
- Rust 2018 macro export pain HOT 3
- gcc error while testing HOT 3
- Release 0.12.2? HOT 8
- Chaining errors from spawned threads.
- Use feature specific links in error_chain! macro
- Add a feature gate to call DebugBreak on construction
- no rules expected this token in macro call HOT 2
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 error-chain.