Marco Ieni
Marco Ieni
I agree it's really complicated. If someone wants to improve this a PR is welcome.
So from my understanding we could: - fix the not correct statement in the rust book. - say that this makes developer life more difficult. Am I right?
> thiserror (library) and anyhow (application) is what I mostly use. Yes, me too. If you take a look at the last paragraph he mentions thiserror as a way to...
I disagree. I feel like not using thiserror and writing all that boilerplate is an anti pattern 😅
Yeah, I see what you mean but I don't share that point of view, because thiserror is not exposed to external users of your library (on the contrary of anyhow...
Should we keep this opened? I mean that's something that we cannot control..
Ok, but I prefer to wait for the actual fix instead of adding `# fn main()` all over the place.
Markdownlint allows this check, it is sufficient to add this to `.markdownlint.yaml`: ```yaml MD004: style: dash ``` The bad news is that it is not automatically fixed with `markdownlint -f...
I think we can consider this issue blocked by [this](https://github.com/DavidAnson/markdownlint/issues/351), right?
Should this be an idiom?