Assuming you’re using Xcode 4, it’s likely that the dependency checker is confused because there are .h files in list of C files to be compiled. So…. Navigate to your target’s “Build Phases” tab. (Click on the project, then click on the target’s name, then click on the “Build Phases” tab.) Ensure that you didn’t … Read more
You can either: Add an allow attribute on a struct, module, function, etc.: #[allow(dead_code)] struct SemanticDirection; Add an allow as a crate-level attribute; notice the !: #![allow(dead_code)] Pass it to rustc: rustc -A dead_code main.rs Pass it using cargo via the RUSTFLAGS environment variable: RUSTFLAGS=”$RUSTFLAGS -A dead_code” cargo build
This is not a bug, but “feature”: For a string, dynamic array, method pointer, or variant result, the effects are the same as if the function result were declared as an additional var parameter following the declared parameters. In other words, the caller passes an additional 32-bit pointer that points to a variable in which … Read more
Be explicit It depends on what you are trying to achieve. The governing rule is It is better to be explicit. Omitting the cases simply makes it look like you forgot some. Being explicit assures subsequent readers of your code that you intended to do nothing for certain events. In light of that, you have … Read more
I think @Yishai has the right of it (I’ll give him an up-vote for getting the ball rolling). I run into this all the time. In what I think was a horrible decision for the Java language, they decided it would be alright to allow classpath settings to go into the MANIFEST files inside jar … Read more
No, you can’t currently in GHC 9.2.1. The {-# OPTIONS_GHC #-} pragma is file-header only and applies to the whole module. And there are no such pragmas (or other ways) to suppress warnings in specific locations. You can check the full list of pragmas in the Haskell user guide: https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/glasgow_exts.html#pragmas The list of warnings might … Read more
I was able to get this to work. My solution looks something like this: <PropertyGroup> <TargetFramework>netcoreapp2.1</TargetFramework> <RuntimeFrameworkVersion>2.1.1</RuntimeFrameworkVersion> <NoWarn>0169;8019</NoWarn> </PropertyGroup> <NoWarn> is PascalCase rather than camelCase, and the element is nested inside of a <PropertyGroup>.
Are you using someone’s dll (or your own) which had implemented this attribute (with exactly the same name) itself as a means of using some c# 3.0 features on pre .Net 3.5 runtimes? (A common trick) This is the probable cause. Since it is using the correct one (the MS one in the GAC) this … Read more
Since C++17 you can use the [[nodiscard]] attribute. Example: [[nodiscard]] int bar() { return 42; }
It is clearly a compiler bug, and it was introduced in C# 3.0 — right around the time that I heavily refactored the reachability checker. This is probably my bad, sorry. The bug is completely benign; basically, we just forgot a case in the warning reporter. We generate the reachability information correctly; as others have … Read more