pacak
pacak
Current implementation looks for significant drops, that can change the behavior, but that's not enough - value might not have a `Drop` itself but one of its children might have...
I think this should be an error. https://github.com/flox/flox/issues/1010
### Problem You can pass `--json=artifacts` to `rustc` and it will emit json messages like `{"$message_type":"artifact","artifact":"/path/to/target/release/deps/libsample-fb5d74408737397e.rlib","emit":"link"}` to `stderr`. `cargo` then parses them and mostly ignores: https://github.com/rust-lang/cargo/blob/a59aba136aab5510c16b0750a36cbd9916f91796/src/cargo/core/compiler/mod.rs#L1803-L1810 later emitting its own...
``` Haddock coverage: 28% ( 5 / 18) in 'Data.Thyme.Format.Internal' Missing documentation for: Module header utf8Char (src/Data/Thyme/Format/Internal.hs:32) utf8String (src/Data/Thyme/Format/Internal.hs:33) shows02 (src/Data/Thyme/Format/Internal.hs:45) shows_2 (src/Data/Thyme/Format/Internal.hs:50) shows03 (src/Data/Thyme/Format/Internal.hs:54) showsYear (src/Data/Thyme/Format/Internal.hs:61) fills06 (src/Data/Thyme/Format/Internal.hs:70) drops0...
- drop dependency on tap - it's not actually used - .entries will call into_iter() on its own - no need to do that
Since version 1.1.2.0 pretty provides the same class as prettyclass does so later is no longer required. Simple removal of prettyclass does the trick for ghc 7.10, better constraints might...
When you run it in a big workspace it starts outputting information about hundreds or thousands types as it encounters them (and then just fails to compile with some strange...
Had do change Show instance a bit, but other than that - works and compiles fine without warnings for ghc 7.6, 7.8 and 7.10
This should let making tests even easier, adds a dependency on an external crate
``` % rust-analyzer --version rust-analyzer f1d7f98ed 2021-09-20 stable ``` ``` % rust-analyzer ssr 'fn $a() -> $d { $e } ==>> pub fn $a() -> $d { $e }' thread...