rust-simple_logger
log
| rust-simple_logger | log | |
|---|---|---|
| 1 | 28 | |
| 217 | 2,060 | |
| - | 1.9% | |
| 6.7 | 8.6 | |
| 4 months ago | about 1 month ago | |
| Rust | Rust | |
| MIT License | 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.
rust-simple_logger
-
Rust cli example #2: Ferris hunts errors
As a backend facility, we will use the simple_logger crate. This crate will simply output messages formatted like this 2015-02-24 01:05:20 WARN [logging_example] This is an example message. I like the crate because it is simple to use and a good fit for small projects. Also, I contributed to another project (rust-riemann-client) maintained by the same author @borntyping (hello Sam) and, it was really an excellent experience. Sources
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.
What are some alternatives?
gophers - Gopher artwork (Golang mascot)
slog - Structured, contextual, extensible, composable logging for Rust
tracing - Application level tracing for Rust.
log4rs - A highly configurable logging framework for Rust
env_logger - A logging implementation for `log` which is configured via an environment variable.
async-anyhow-logger - An easy crate for catching anyhow errors from an asynchronous function, and passing them to your logger
InputBot - Rust library for creating global hotkeys, and simulating inputs
nvim-rs - A rust library for neovim clients
rust-cli-boilerplate - Rust project boilerplate for CLI applications
epoch-converter - epoch-converter enables conversion between seconds and units of time as well as between an epoch timestamp and units of time.
rand - A Rust library for random number generation.
cctools-port - Apple cctools port for Linux and *BSD