Paul Loyd

The `clear()`/`drain()` methods?

1

It would be nice to have `DynStack::clear()` and/or `DynStack::drain()` (without arguments) methods.

The current implementation cannot utilize fully task at the end of each `Insert`: 

* Number of inserted bytes (compressed) * Number of inserted bytes (uncompressed)

Right now it can be done using separate arrays: ```rust #[derive(Debug, Row, Serialize, Deserialize)] struct MyRowOwned { no: u32, #[serde(rename = "nested.a")] a: Vec, #[serde(rename = "nested.b")] b: Vec, }...

The fetch API is unsound if used with borrowed types

6

The current API allows the following code: ```rust let mut cursor = client.query("...").fetch::

Use `RowBinaryWithNamesAndTypes`

4

Use `RowBinaryWithNamesAndTypes` instead of `RowBinary` as a primary format in order to support `deserialize_any` and, hence, `serde(flatten)` and type conversions & validation.

Client should respect the "Keep-Alive" header

2

It seems that hyper doesn't respect the `Keep-Alive` header and just uses a predefined value (`90 seconds`). Instead, hyper should consider the header and rotate connections according to it. Related...

How to use a new handle-based API?

15

I'm writing an actor system ([elfo](https://github.com/elfo-rs/elfo/)) and have been faced with inconvenient usage of the handle API that has been lent in the last metrics release (0.18). Some prelude before...

Use SSO in `SharedString`

1

Shouldn't name/labels use [`SmartString`](https://docs.rs/smartstring/latest/smartstring/) inside? Almost all dynamic label values in my production fit in 23 bytes. Also, values of `u64` also fit in 23 bytes. IPv4+port also fits into...

How to handle status codes: 429 (TooManyRequest) and so on?

1

It seems that the implementation [ignores status codes at all](https://docs.rs/telegram-bot/0.6.3/src/telegram_bot/connector/hyper.rs.html#69). Thus, it's impossible to detect rate limit violations and handle them. Is that right?