log
log copied to clipboard
rust-lang
Logging implementation for Rust
Currently this crate uses `SeqCst` orderings for all atomic operations related to logger initialization. At most these orderings would need to be `AcqRel` since they only involve a single atomic....
When writing command line programs, I often find myself wanting two distinct "info"-like log levels: one for regular output and one when a `--verbose` flag is requested by the user....
There is almost no information / clarity on what `flush()` should do and if it's called by any of the macros in this crate. I think it should say something...
Hi, I read the docs and find that the log filter level can only be set at complie time, I tested the `set_max_level()`function, can only find the max_level changed, but...
When building very large projects with multiple layers of dependent crates, it can be useful to limit, at compile-time, the overall logging to a less verbose level like Info or...
https://github.com/rust-lang/log/runs/6683448799?check_suite_focus=true#step:3:6 ``` error: DEPRECATED: future versions of rustup will require --force-non-host to install a non-host toolchain as the default. warning: toolchain 'stable-x86_64' may not be able to run on this...
Out of privacy concern I don't want to include references to the file and lines so as to make reverse engineer harder, but far as I see there is no...
```rust pub fn logger() -> &'static dyn Log { // Is it necessary to use Ordering::SeqCst in log! if STATE.load(Ordering::SeqCst) != INITIALIZED { static NOP: NopLogger = NopLogger; &NOP }...
`log`'s `build.rs` file is very simple. It just checks the target platform and then tells Cargo to pass in `--cfg=atomic_cas` and/or `--cfg=has_atomics` as necessary. Those conditions are then used in...
This is part of #328 I think we've explored enough of this design space now and the API has been in use within the `tide` project for some time now...
