Nemo157

One thing I don't see mentioned in the RFC is whether `use`ing trait aliases brings methods into scope? (see the [next comment](https://github.com/rust-lang/rust/issues/41517#issuecomment-403568840) for a correct example, mine was wrong).

Personally I also don't care about having the artifacts copied anywhere, I access them via `cargo run` etc. directly from the work-dir anyway. It'd be nice if we could do...

> If you are only running your project via `cargo run` I don't think you need to worry about the exact location of the binary in the `target` dir? One...

> I wrote a test program which compares async_compression vs the existing zstd crate, and it's just async_compression that fails to decompress archives with skippable frames. By default async-compression only...

I agree with this, I keep getting confused with `/` retaining the current text too.

To test it out locally I'm trying this out now: ```zsh _atuin_search_viins_clear() { BUFFER= _atuin_search_viins } zle -N atuin-search-viins-clear _atuin_search_viins_clear bindkey -a / atuin-search-viins-clear ``` it's not quite right though,...

> more flexible to pick the same version as dependant or sibling dependencies. This is just not something that cargo supports in general. If you want the same version as...

As mentioned this doesn't occur normally because the binary result format is used. I managed to trigger it without editing `sqlx-core` to override that by using the direct text query...

> My expectations are, if I store a date: 2024-01-01T00:00:00-07:00, I expect the decoded value to be the same 2024-01-01T00:00:00-07:00 and NOT 2023-12-31T17:00:00-00:00 Note that Postgres does _not_ store timezones....

> All timezone-aware dates and times are stored internally in UTC. They are converted to local time in the zone specified by the [TimeZone](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE) configuration parameter before being displayed to...