Failing to return a value from a function that has a non-void return type results in undefined behaviour, but is not a semantic error. The reason for this, as far as I can determine, is largely historical. C originally didn’t have void and implicit int meant that most functions returned an int unless explicitly declared … Read more
Are you using Maven or Gradle for your project? I had the same issue with Gradle, but I was able to remove the warnings by putting the -Xuse-experimental=kotlin.Experimental in my build.gradle file, inside a tasks.withType. For KtorExperimentalLocationsAPI you could try: tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).all { kotlinOptions.freeCompilerArgs += [“-Xuse-experimental=io.ktor.locations.KtorExperimentalLocationsAPI”] }
There does not appear to be a warning option built in to gcc or clang that does what is requested. However, we can use clang-query instead. Below is a clang-query command that will report comparison of 32-bit and 64-bit integers, on the assumption that int is 32 bits and long is 64 bits. (More about … Read more
Ensure the files are under the gen folder, the typical home for all generated .java files. Then in the project properties, under Java Build Path, set Ignore optional compile problems for that folder to Yes. If your project structure requires your files be in a folder other than gen, add that folder to the Java … Read more
The compiler cannot tell from that code if the function will ever reach the end and still return something. To make that clear, replace the last else if(…) with just else.
This appears to be a bug in gcc at least. The following code: #pragma GCC diagnostic ignored “-Wunknown-pragmas” #pragma GCC diagnostic ignored “-Wuninitialized” int fn(void) { #pragma xyzzy int x; return x; } int main (void) { return fn(); } has no problems ignoring the uninitialised x value but still complains about the pragma (without … Read more
There’s no real problem here. In C and C++, the compiler is allowed to insert padding after struct members to provide better alignment, and thus allow faster memory access. In this case, it looks like has decided to place smap on an 8-byte alignment. Since an int is almost certainly four bytes, the warning is … Read more
There does not appear to be a warning option built in to gcc or clang that does what is requested. However, we can use clang-query instead. Below is a clang-query command that will report comparison of 32-bit and 64-bit integers, on the assumption that int is 32 bits and long is 64 bits. (More about … Read more
Try cleaning the Java language server workspace: Cmd + Shift + P (Ctrl + Shift + P on Windows) to show the command palette Choose “Java: Clean the Java language server workspace” Restart and Delete It just worked for me.
Try doing this: #pragma GCC diagnostic ignored “-Wuninitialized” foo(b); /* no diagnostic for this one */ This pragma comes in three interesting and helpful flavors : warning, error, ignored. See 6.56.10 Diagnostic Pragmas for their usages. The link says, GCC allows the user to selectively enable or disable certain types of diagnostics, and change the … Read more