"always name threads" guideline?

[Ben-PH]

instead of

std::thread::spawn(...);

use

std::thread::Builder::new().name("useful-name-here").spawn(...).unwrap();

Not so sure why a builder-based spawn gives a Result. Not so sure what a good pattern for handling a builder-spawn error might be.

What are your thoughts?

[AurelienFT]

Yes. We should be more attentive at review but naming thread must be a convention in our code.