Jane Losare-Lusby
Jane Losare-Lusby
> are you sure? I should note that I had to make similar changes to `color-backtrace` and there are ... problems ... that need to be resolved. Specifically, I don't...
> @yaahc If you are still interested in this, maybe you could answer the questions by @niklasmohrin? Otherwise, I'd like to close this. I'm not sure the exact best way...
Also, a bit more context from the lang team meeting. When we discussed this we agreed that we want the reference to include documentation about the runtime half of the...
> RE. the above (w/ the context from reading the minutes of that aformentioned meeting after the fact), C requires that a status code `0` (and incidentally also `EXIT_SUCCESS` which...
I think there's been some confusion here. I didn't mean to imply that `ExitCode::from(20u8)` would always map directly to `ExitCode::FAILURE`. I am just trying to make sure that cross platform...
I think I might also be running into the same issue in `rust-lang/rust`. https://github.com/rust-lang/rust/blob/master/library/core/src/cell/once.rs#L125 produces a "`Err(_)` not covered" error in rust-analyzer as of the `c9e134e1b609e571f4d7d18f91f0ccb1a0cb685d` commit in `rust-lang/rust`. Not...
@burdges this is a general restriction on Any and downcast on Error types, I don't think it's currently possible to downcast types that aren't : 'static The second design with...
@kennytm There was a specific soundness issue which caused @mystor to add the double lifetime, though I don't remember what it was. Overall I'm definitely in favor of removing the...
> Firstly, the return type `ProvideResult` is unnecessarily complex in order to support `?`. This type actually only has 2 states: fulfilled or not. This is isomorphic to a bool....
I lean towards preferring a design that makes `Request` generally usable, but I otherwise agree with all of your changes @kennytm, so I'm going to pull in your branch and...