Do you think there's a coordinated campaign by(?) Coverity to get your open source project to use it? For what reason? It's surely not to make money considering Coverity gives open source projects a free license.
> I have nothing against Coverity personally - it may very well help the V code generator, but I hate being forced to use a product in such a way.
Yes, two random people telling you to consider using a static analysis tool is "forcing" you to use a product.
----
This is a great example why everyone should stay away from V. Industry standard best practices are treated as conspiracy theories by the developers.
It's fine for people to decide they want to make a new language; that's great! It's also totally fine for all of those people to have no idea what they're doing; that's how you learn. But at some point, you need to recognize that you don't know what you don't know. V is not anywhere close to the level of production ready-ness you yourself have repeatedly claimed.
I personally, find the following course of events very interesting:
On 2020/09/14, a Discord user named `Engineer` writes the following:
> We should consider using Coverity as this is an opensource github project - we can test the output v filename.v -o filename.c as input for Coverity - to help us understand issues with the generated C code.
Mind you, that is not a code contributor, and his earlier questions, are about a mysterious undisclosed C compiler, that produces much more stricter error messages than gcc's ones.
Then he makes a short lecture on the topic of `What is static analysis?` again on Discord...
It is a Scooby Doo mystery indeed.
I have nothing against Coverity personally - it may very well help the V code generator, but I hate being forced to use a product in such a way.