These are chat archives for rust-lang/rust
Self.f. Note also that
Self, so it must call some other non-defalt fn which produces
--releaseand is immediate in debug mode (this is not compilation time), using recent-ish a few days old nightly. does this sound like a known bug? currently trying to triangulate this with
debug!(...)logging and recompilation which is a bit slow :)
let file = std::fs::OpenOptions::new().read(true).open(&self.path).map_err(CustomErrorType)?;
CustomErrorTypeis using error_chain so probably backtrace?
RUST_BACKTRACE=0, also it'd seem that no backtrace is ever generated..
RUST_BACTRACEwas super slow, even for an empy file
rustc 1.19.0-nightly (5f3966864 2017-05-25)with error_chain 0.8.1, let's try updating to latest nightly
rustcfor allocating stactraces tends to allocate massive amount of information, and now one understands why.
error_chainuses it's own backtrace collecting machinery, and I bet it uses the same underlying library, and is susceptible to the exact same problem! It might be a good idea to rise an issue on
error_chainand link to the one from
.unwrap(), and I get to watch in slow motion as the functions are found, it's fast up until 9th step, then taking much longer on step 10, rest are fast
10: <core::iter::Map<I, F> as core::iter::iterator::Iterator>::next at /checkout/src/libcore/result.rs:737 at src/db/checkpoint.rs:183 at /checkout/src/libcore/ops.rs:2633 at /checkout/src/libcore/ops.rs:2731 at /checkout/src/libcore/option.rs:398 at /checkout/src/libcore/iter/mod.rs:1065 at /checkout/src/libcore/iter/mod.rs:1065
does anybody know why the JsonNode type allows indexing with
 but not
that is you can get a field by string, but not with an int
backtracelibrary. I'm stuck on an old version of
error-chainuntil errors are
Sendagain so hopefully I don't get stuck :smile: