Hadrien G. comments

Results 82 comments of


                                            Hadrien G.

Consider using field names for anonymous types/unions

> There might be name collisions if two structs have fields with the same name. So that means that we cannot drop the number suffix at the end in all...

nextest seems to handle stdio-intensive tests less efficiently than cargo test

First things first : for a reproducer you can... - Install the libhwloc development package of your preferred package manager - Clone [the repo of my project](https://github.com/HadrienG2/hwlocality) - Checkout commit...

nextest seems to handle stdio-intensive tests less efficiently than cargo test

> To be honest, I can't reproduce this. With a Ryzen 7950x and Linux kernel 6.5.6 and Rust 1.73.0, with [this test](https://gist.github.com/sunshowers/85712961477ed07c6a241a8f3098402f) that writes roughly 500MiB, I get: > >...

nextest seems to handle stdio-intensive tests less efficiently than cargo test

> cargo test does its output collection in-process, without using OS pipes. That might explain the difference. Sounds pretty neat, is there a way nextest could leverage the same infrastructure?...

nextest seems to handle stdio-intensive tests less efficiently than cargo test

How would you feel about an upstream feature that dumps the stdio buffer when a certain signal (say, SIGUSR1) is received? I think it is the minimal upstream change that...

nextest seems to handle stdio-intensive tests less efficiently than cargo test

I would obviously be fine with a "wontfix please silence your panics" resolution since I already have a panic handler that does this around ;)

What would be needed for an array-based version of Itertools::tuples(), etc?

Array patterns [are already available in unstable form](https://play.rust-lang.org/?gist=7a5df535ef9488dfcf497f0b66347005&version=nightly), but I can understand why you would want to wait for const generics as well. Otherwise, we would end up replacing one...