Kani should not print warnings about concurrency primitives (as long as it's single-threaded) #1460
Labels
[C] Feature / Enhancement
A new feature request or enhancement to an existing feature.
As mentioned in #1452 (comment), users will often be greeted by messages of the form
Kani does not support concurrency for now.
{}in {} treated as a sequential operation.
. For instance, if you're compiling tokio, you get the following output:This causes several problems:
I agree that we have to be careful about this if/when we introduce multi-threading, but printing warnings all the time does not seem to be the best path forward to me.
The text was updated successfully, but these errors were encountered: