Simonas Kazlauskas

`create` callback could be made `?Sized`

1

Internally `DynamicPool` will box the callback, so there isn't a good reason to prevent something like `DynamicPool T>` from being specified.

Introduce a lifetime generic to `Visit` in order to allow borrowing out specific parts of the `valuable::Value` during visits

1

## Motivating use-case My motivating use-case is to write down in `tracing 0.2` a visitor that is able to borrow `Event`’s `message`. Doing so today is impossible even though lifetimes...

1. Checkout `github:openhab/openhab-distro/00e00fa5bf105aa554ab2cf44e7a8cebfcd046bb`; 2. Run `mvn org.nixos.mvn2nix:mvn2nix-maven-plugin:mvn2nix -B` Observe mvn2nix fail with a `NullPointerException`. Output ``` [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] openHAB Distribution...

Consider changing `Registry::register/unregister` to remove the `Box` in the argument

3

Currently `register` and `unregister` methods of `Registry` take `Box`, however in practice this means that most calls of this method will end up looking like this: ```rust let metric =...

Consider replacing most owned data with a `Cow<'static, _>` where it is plausible to carry static data

1

Currently a large number of APIs deal directly with owned strings, however in my experience most APIs deal with data that is most likely static: labels & sometimes their values,...

A future-based drain for the asynchronous future

7

With futures and async coming into the rust standard library, proper, perhaps slog-async should grow some support for a `Future` to act as the other end of a `Drain`? This...

``` # rustc version rustc 1.72.0-nightly (f0411ffce 2023-05-30) # docs.rs version docsrs 0.6.0 (a5028966 2023-05-14) # build log [INFO] running `Command { std: "docker" "create" "-v" "/home/cratesfyi/workspace/builds/finite-wasm-0.5.0/target:/opt/rustwide/target:rw,Z" "-v" "/home/cratesfyi/workspace/builds/finite-wasm-0.5.0/source:/opt/rustwide/workdir:ro,Z" "-v"...

Not every runtime will reserve the entire stack frame for a given function at the beginning of the function execution. Our current stack analysis can only reserve stack use at...

They may want to specify that e.g. some pure instructions are impure in their runtime for some reason (maybe they use a host function call internally to implement it?) or...