rust-typed-builder VS console

derive_builder works in runtime - you have to unwrap built result. And code editors cannot use auto-import builder-types. That's why I switched to [typed-builder|https://github.com/idanarye/rust-typed-builder] which looks similar to builder-pattern but more popular.

I'm the author of the typed-builder crate (and a couple of other crates in a similar position). The name of the crate's repository on GitHub is rust-typed-builder. Does the new trademark policy mean I have to change the repository's name to typed-builder-rs or typed-builder.rs or something similar, or am I in the clear because only the repository name is has the word "rust" in it and the crate itself is only named "typed-builder"?

There are also crates which can do that for you (e.g. https://github.com/idanarye/rust-typed-builder).

I can open a PR if desired but typed-builder is a big example for me of where this would be super useful. It's a good example of using traits/type safety for compile-time guarantees but the error messages are really subpar compared to the standard Rust experience, so feels like a very arbitrary compromise on Rust's strengths.

Yes! The inspiration came from: * rust-typed-builder which is the struct equivalent of this crate. * https://users.rust-lang.org/t/typesafe-builder-design/58784

Rust Typed Builder

tokio-console is a debugger for Rust async programs that use Tokio. To get started, add the console-subscriber crate to your project and add the following line which will initialise the subscriber and allow tokio-console to connect to it:

You could try https://github.com/tokio-rs/console to debug and profile what happens with tokio tasks in your program.

The tokio-console CLI is a fun one. The console-subscriber supports shipping to a console server running elsewhere, apparently. That gives you a window into what's happening now.

Tokio console maybe? https://github.com/tokio-rs/console

If I add "console_subscriber::init()" line as https://github.com/tokio-rs/console recommends, tracing_subscriber cannot be initialized.

I'm building an HTTP load tester called pdc! I have run out of obvious (to me at least) places to look for performance gains. I'm achieving around 45,000 requests per second, per core. Right now I'm using hyper with a separate tokio runtime (in current thread mode) running on each core. So far having runtime on each core/NUMA node has really helped with cache coherency. Any recommendations for profiling beyond tokio console or tokio metrics (Convenient timing amirite!)?

It was just an accident and has been fixed https://github.com/tokio-rs/console/issues/270.

P.S. Tokio [now also has Tokio Console](https://github.com/tokio-rs/console) allowing you to conveniently troubleshoot your tasks if they are causing issues :)

You can opt-in to async runtime such as tokio, and you can use tokio-rs/console for it's top-like metric