From a live table (there are about 10 of these in the database): sqlite> select count(*) from <redacted>; 49862386 Curious what row count you expect in non-SQLite databases on a regular basis.
Yes except when given a std::thread you don't know whether it will join in the destructor whereas with jthread you do. I personally don't know how it helps. But I'm sure the proposals had some reasoning.
It's useful because you may be able to make compile-time decisions on the basis of the type of thread you're dealing with. What those are, I don't know. As for instantiations, an astute library developer will be able to…
The main reason is so that the type system knows which thread is which and can handle it differently. They may still inherit from the same implementation and do what you suggest though.
From a live table (there are about 10 of these in the database): sqlite> select count(*) from <redacted>; 49862386 Curious what row count you expect in non-SQLite databases on a regular basis.
Yes except when given a std::thread you don't know whether it will join in the destructor whereas with jthread you do. I personally don't know how it helps. But I'm sure the proposals had some reasoning.
It's useful because you may be able to make compile-time decisions on the basis of the type of thread you're dealing with. What those are, I don't know. As for instantiations, an astute library developer will be able to…
The main reason is so that the type system knows which thread is which and can handle it differently. They may still inherit from the same implementation and do what you suggest though.