log
slog
Our great sponsors
log | slog | |
---|---|---|
28 | 2 | |
2,049 | 1,530 | |
2.7% | 1.5% | |
8.6 | 6.9 | |
21 days ago | about 1 month ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
log
-
What Are The Rust Crates You Use In Almost Every Project That They Are Practically An Extension of The Standard Library?
log: Logging interface with various levels.
-
How easy is it to swap out your async runtime?
Depends on your logging crate. log does not depend on any async runtime.
-
log is going to bump msrv to 1.60
See the corresponing PR: https://github.com/rust-lang/log/pull/543
-
Rust and its friendly crates: Don't miss out on them!
log
-
Colorful logging with pizzazz!
It's a for-fun project that provides a configurable implementation for the log crate. This language and community is awesome, and I hope some of you get a kick out of this!
-
Ergonomic logging?
Firstly I would start by taking a look at how crates using log actually resolve this. Particularly the set_boxed_logger which simply calls Box::leak.
-
Logging Crate for CLI?
You might want to look at log and simple_log.
- Hey Rustaceans! Got a question? Ask here! (36/2022)!
-
Rust playground on iOS
4) Another route that I tried is to develop a simple terminal app using SwiftUI with a Xcode project to build that app + link against a Rust library compiled for iOS with the actual logic. I used swift-bridge for this and it works really well, to the point where I have a custom logger that you can simply use the print stuff to SwiftUI from Rust using the log crate. Once I have a bit more time, I will probably try figuring out how to clean this up a bit more.
slog
-
I'm releasing cargo-sandbox
I only recently learned about rustwide myself when implementing sandboxed rustdoc builds for Shipyard.rs. After spending a good amount of time with the codebase, I have found it to be generally high quality, but the way the code is organized makes it fairly difficult to adapt for different purposes than it was intended for (not modular). I have a fork that I have changed to do what I need but not sure whether the two codebases can be reconciled because I ended up needing to put stuff very specific to my purposes in there. I also ran into a weird issue where the logging from rustwide was conflicting with the slog-based logging from my code, which feels to me like there is some UB lurking somewhere.
-
Adding Slog Logger to Actix Web
Slog Core Crate : core package to the gateway of logging modules.
What are some alternatives?
tracing - Application level tracing for Rust.
log4rs - A highly configurable logging framework for Rust
rust-simple_logger - A rust logger that prints all messages with a readable output format.
angle-grinder - Slice and dice logs on the command line
env_logger - A logging implementation for `log` which is configured via an environment variable.
actix-slog-logger-setup - Adding Slog Logger to Actix Web easily.
async-anyhow-logger - An easy crate for catching anyhow errors from an asynchronous function, and passing them to your logger
crosvm - The Chrome OS Virtual Machine Monitor - Mirror of https://chromium.googlesource.com/crosvm/crosvm/
InputBot - Rust library for creating global hotkeys, and simulating inputs
async - Asynchronous drain for slog-rs v2