The count method of NSArray returns an NSUInteger, and on the 64-bit OS X platform NSUInteger is defined as unsigned long, and unsigned long is a 64-bit unsigned integer. int is a 32-bit integer. So int is a “smaller” datatype than NSUInteger, therefore the compiler warning. See also NSUInteger in the “Foundation Data Types Reference”: … Read more
You can either: Add an allow attribute on a struct, module, function, etc.: #[allow(dead_code)] struct SemanticDirection; Add a crate-level allow 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
Playing off of Michael E’s comment: #if defined(__GNUC__) #define DEPRECATE(foo, msg) foo __attribute__((deprecated(msg))) #elif defined(_MSC_VER) #define DEPRECATE(foo, msg) __declspec(deprecated(msg)) foo #else #error This compiler is not supported #endif #define PP_CAT(x,y) PP_CAT1(x,y) #define PP_CAT1(x,y) x##y namespace detail { struct true_type {}; struct false_type {}; template <int test> struct converter : public true_type {}; template <> struct … Read more
Setters and Getters apply to computed properties; such properties do not have storage in the instance – the value from the getter is meant to be computed from other instance properties. In your case, there is no x to be assigned. Explicitly: “How can I do this without explicit backing ivars”. You can’t – you’ll … Read more
I’ve only ever used Class.cast(Object) to avoid warnings in “generics land”. I often see methods doing things like this: @SuppressWarnings(“unchecked”) <T> T doSomething() { Object o; // snip return (T) o; } It’s often best to replace it by: <T> T doSomething(Class<T> cls) { Object o; // snip return cls.cast(o); } That’s the only use … Read more
In the expression (i, ++i, 1), the comma used is the comma operator the comma operator (represented by the token ,) is a binary operator that evaluates its first operand and discards the result, and then evaluates the second operand and returns this value (and type). Because it discards its first operand, it is generally … Read more
I think that a custom annotation, which will be processed by the compiler, is the solution. I frequently write custom annotations to do things at runtime, but I never tried to use them at compilation time. So, I can only give you pointers on the tools you may need : Write a custom annotation type. … Read more
Macro names should only consist of alphanumeric characters and underscores, i.e. ‘a-z’, ‘A-Z’, ‘0-9’, and ‘_’, and the first character should not be a digit. Some preprocessors also permit the dollar sign character ‘$’, but you shouldn’t use it; unfortunately I can’t quote the C standard since I don’t have a copy of it. From … Read more
You can’t. The manual for GCC 4.4.0 is only comprehensive for that version, but it does list all the possible warnings for 4.4.0. They’re not all on the page you link to though, for instance some language-specific options are on the pages for C++ options or Obj-C options. To find them all you’re better off … Read more
It depends on your IDE or compiler. Here is a list for Eclipse Galileo: all to suppress all warnings boxing to suppress warnings relative to boxing/unboxing operations cast to suppress warnings relative to cast operations dep-ann to suppress warnings relative to deprecated annotation deprecation to suppress warnings relative to deprecation fallthrough to suppress warnings relative … Read more