dtolnay/thiserror issues and pull requests

#245 - Suggestion: Automatically generate documentation comments based on display string

Issue - State: closed - Opened by naturecodevoid about 1 year ago - 1 comment

#244 - Add no_std support

Pull Request - State: closed - Opened by mina86 about 1 year ago - 1 comment

#243 - update error generic member access

Pull Request - State: closed - Opened by waynr about 1 year ago - 4 comments

#242 - Fix access to `write!` macro when `thiserror` is not in scope

Pull Request - State: closed - Opened by dtolnay about 1 year ago

#241 - New release breaks callers of the Error derive if it came from a re-export from another crate

Issue - State: closed - Opened by NiseVoid about 1 year ago - 2 comments

#240 - Avoid calling a nonstandard write! macro that might be in scope

Pull Request - State: closed - Opened by dtolnay about 1 year ago - 1 comment

#239 - Macro derive fails when a non-std write macro is in scope

Issue - State: closed - Opened by konstin about 1 year ago - 2 comments

#238 - error[E0635]: unknown feature `proc_macro_span_shrink`

Issue - State: closed - Opened by cacilhas about 1 year ago - 1 comment

#237 - Change type in formating example

Pull Request - State: closed - Opened by Gordon01 over 1 year ago

#236 - Unresolved import 'thiserror' when adding a Backtrace to an enum struct

Issue - State: closed - Opened by JustAnotherCodemonkey over 1 year ago - 7 comments

#235 - Interop with other error libs

Issue - State: closed - Opened by hcldan over 1 year ago - 2 comments

#234 - Add support for the `alterante` flag.

Issue - State: closed - Opened by xfbs over 1 year ago - 1 comment

#233 - Make use of alternate() flag

Pull Request - State: closed - Opened by xfbs over 1 year ago

#232 - A modest proposal for no_std support

Issue - State: closed - Opened by udoprog over 1 year ago - 2 comments

#231 - `anyhow::Error` as `#[source]` does not work generically

Issue - State: closed - Opened by chbaker0 over 1 year ago - 2 comments

#230 - [1.71 nightly] error: the `#[proc_macro_derive]` attribute is only usable with crates of the `proc-macro` crate type

Issue - State: closed - Opened by Originalimoc over 1 year ago - 2 comments

#229 - Strange error with `#[from]`.

Issue - State: closed - Opened by BratSinot over 1 year ago - 1 comment

#228 - Unresolved import and unstable library feature errors on Rust 1.68.2

Issue - State: closed - Opened by vincent-herlemont over 1 year ago - 2 comments

#227 - Update to syn 2

Pull Request - State: closed - Opened by dtolnay over 1 year ago - 1 comment

#226 - Eliminate unneeded use of Spanned trait on single tokens

Pull Request - State: closed - Opened by dtolnay over 1 year ago

#225 - [Enhancement] Better From impl ?

Issue - State: closed - Opened by GilShoshan94 over 1 year ago - 2 comments

#224 - Specifying #[from] without exposing underlying error

Issue - State: closed - Opened by Artem-Romanenia over 1 year ago - 1 comment

#223 - Avoid generating code using unstable features for std::backtrace

Pull Request - State: closed - Opened by andrewaylett over 1 year ago - 2 comments

#222 - Anyhow debug impl doesn't log the debug of the error cause

Issue - State: closed - Opened by DanielBauman88 over 1 year ago - 1 comment

#221 - Forbid unsafe code

Pull Request - State: closed - Opened by RomFouq over 1 year ago

#220 - `provide_any` getting enabled on stable

Issue - State: closed - Opened by akriegman over 1 year ago - 1 comment

#219 - Nested Errors Question

Issue - State: closed - Opened by tr3ysmith over 1 year ago - 1 comment

#218 - Catching Serde deserializer error

Issue - State: closed - Opened by 0cv over 1 year ago - 1 comment

#217 - New macro syntax: `#[from(T)]`

Issue - State: closed - Opened by Kinrany over 1 year ago - 1 comment

#216 - I'm trying to wrap my head around the process of creating a derive macro. How much inspiration can I take from your code before I need a license?

Issue - State: closed - Opened by NullSurplus over 1 year ago - 1 comment

#215 - `std::error::Error` has to be implemented for an enum variant field?

Issue - State: closed - Opened by stijnfrishert almost 2 years ago - 2 comments

#214 - Conflicting ergonomics for source chains

Issue - State: closed - Opened by Ralith almost 2 years ago - 4 comments

#213 - Generate a default Display value if the #[error] attribute is missing from an enum entry

Issue - State: closed - Opened by sazzer almost 2 years ago - 1 comment

#212 - Cannot use `trait Custom: std::error::Error` as boxed source due to sealed `AsDynError`

Issue - State: open - Opened by Byron almost 2 years ago - 3 comments

#211 - no_std support on nightly

Pull Request - State: closed - Opened by FlorianUekermann almost 2 years ago - 5 comments

#210 - Use with should_panic

Issue - State: closed - Opened by nzakas almost 2 years ago - 3 comments

#209 - provide_any causes fail in stable channel

Issue - State: closed - Opened by kkolyan almost 2 years ago - 2 comments

#204 - derive(Error) with Backtrace causes errors on beta

Issue - State: closed - Opened by Heliozoa almost 2 years ago - 2 comments

#203 - docs: add `#[error("...")]` example for struct

Pull Request - State: closed - Opened by marcospb19 almost 2 years ago - 1 comment

#202 - fix UI tests missing lifetime annotations

Pull Request - State: closed - Opened by marcospb19 almost 2 years ago - 1 comment

#201 - Consider exposing formatter in display attribute

Issue - State: open - Opened by dtolnay almost 2 years ago - 2 comments

#200 - Add test of Display impl nested inside display attribute

Pull Request - State: closed - Opened by dtolnay almost 2 years ago

#199 - Semver breakage on 1.0.37

Issue - State: closed - Opened by Xaeroxe almost 2 years ago - 4 comments

#197 - Fix documentation mentioning `backtrace()` method

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#196 - add #![no_std] support

Issue - State: closed - Opened by tsatke about 2 years ago - 10 comments

#195 - document that `error(transparent)` works with structs

Pull Request - State: closed - Opened by matklad about 2 years ago

#194 - Clippy does not pass after rustc update.

Issue - State: closed - Opened by ski0090 about 2 years ago - 2 comments

#192 - "#![feature] may not be used on the stable release channel"

Issue - State: closed - Opened by lfrancke about 2 years ago - 17 comments

#191 - Pull in Provider impl from anyhow 1.0.65

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#190 - Fix "Multiple applicable provide methods in scope"

Pull Request - State: closed - Opened by dtolnay about 2 years ago - 1 comment

#189 - Add Sealed supertrait to private AsDynError trait

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#188 - Add test involving backtrace from a Box<dyn Error>

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#187 - Add test of getting backtrace from an anyhow source

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#186 - Add temporary ui test of 'multiple applicable items' error

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#185 - Multiple applicable `provide` methods in scope

Issue - State: closed - Opened by dtolnay about 2 years ago

#184 - Directly call source.provide instead of going through dyn error

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#183 - Re-enable deprecated variants test.

Pull Request - State: closed - Opened by dtolnay about 2 years ago - 1 comment

#182 - Expose backtrace via generic member access

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#181 - Deriving `fmt::Display` from doc comments

Issue - State: closed - Opened by JonathanWoollett-Light about 2 years ago - 1 comment

#180 - Macro for `cause` and `description`.

Issue - State: closed - Opened by BratSinot about 2 years ago - 2 comments

#179 - add error attributs to examples of struct custom error

Pull Request - State: closed - Opened by hiro-o918 about 2 years ago - 1 comment

#178 - [Question] Can the error message from the `#[error(...)]` attribute be returned to the end-user (API)?

Issue - State: closed - Opened by enheit about 2 years ago - 1 comment

#177 - Deriving structs with `backtrace` fails since `fn backtrace` has been removed from `Error`

Issue - State: closed - Opened by Systemcluster about 2 years ago - 4 comments

#176 - Unexpected error strings when mixing positional and named arguments

Issue - State: closed - Opened by erickt about 2 years ago - 1 comment

#175 - Add example for expressions in `error` attribute

Pull Request - State: open - Opened by dnaka91 about 2 years ago - 3 comments

#174 - Wrapping `anyhow::Error` in another error loses backtrace

Issue - State: open - Opened by Ten16 over 2 years ago - 1 comment

#173 - test

Issue - State: closed - Opened by regar42 over 2 years ago

#172 - Making error string optional

Issue - State: closed - Opened by Pzixel over 2 years ago - 1 comment

#171 - #[from] should support Option

Issue - State: closed - Opened by phillord over 2 years ago - 2 comments

#170 - #[error(transparent)] hides wrong error in chain()

Issue - State: closed - Opened by muirdm over 2 years ago - 4 comments

#169 - Conflict impl with std::fmt::Display

Issue - State: closed - Opened by ANUGLYPLUGIN over 2 years ago - 1 comment

#168 - What's the best practice to custom error message?

Issue - State: closed - Opened by TennyZhuang over 2 years ago - 1 comment

#167 - `use thiserror` prevents re-use in piggy-back proc-macros

Issue - State: closed - Opened by drahnr over 2 years ago - 1 comment

#165 - Feature Request: Warnings for error message convention violation

Issue - State: closed - Opened by Jonas-Heinrich over 2 years ago - 1 comment

#164 - Fix miscounting fields when from and backtrace are same field

Pull Request - State: closed - Opened by dtolnay almost 3 years ago

#163 - Unhelpful diagnostic on variant containing #[from] #[backtrace] Error, Backtrace

Issue - State: closed - Opened by dtolnay almost 3 years ago

#162 - from attribute and clone?

Issue - State: closed - Opened by vikigenius almost 3 years ago - 1 comment

#161 - Derive Serialize/Deserialize for external errors which are used with `#[from]`

Issue - State: closed - Opened by oren0e almost 3 years ago - 1 comment

#160 - Support for no_std with a homespun/third-party Error trait

Issue - State: closed - Opened by mzabaluev almost 3 years ago - 2 comments

#159 - Generic on foreign error type

Issue - State: closed - Opened by midnightexigent almost 3 years ago - 2 comments

#158 - `?` couldn't convert the error to `CustomError`

Issue - State: closed - Opened by debuggerpk almost 3 years ago - 1 comment

#158 - `?` couldn't convert the error to `CustomError`

Issue - State: closed - Opened by debuggerpk almost 3 years ago - 1 comment

#157 - Backtrace api and #[from]

Issue - State: open - Opened by steinemann almost 3 years ago

#157 - Backtrace api and #[from]

Issue - State: open - Opened by steinemann almost 3 years ago

#156 - `impl From<T> for T` conflicts with associated error types

Issue - State: closed - Opened by Kinrany almost 3 years ago - 1 comment

#156 - `impl From<T> for T` conflicts with associated error types

Issue - State: closed - Opened by Kinrany almost 3 years ago - 1 comment

#155 - add UnwindSafe impl for AsDynError

Pull Request - State: closed - Opened by cosmicexplorer almost 3 years ago - 2 comments

#155 - add UnwindSafe impl for AsDynError

Pull Request - State: closed - Opened by cosmicexplorer almost 3 years ago - 2 comments

#154 - Can thiserror be converted into from arbitrary errors?

Issue - State: closed - Opened by detly about 3 years ago - 6 comments