The warning message “unchecked conversion” implies that we should check the conversion before the assignment. To check the type conversion, we can go through the raw type collection and cast every element to our parameterized type.

How to resolve warning message: uses unchecked or unsafe operations. You can resolve this warning message by using generics with Collections. In our example, we should use ArrayList rather than ArrayList() . When you will compile above code, you won’t get warning message anymore.

The uses unsafe or unchecked operations warning is displayed when you execute code which the Java compiler considers to be lacking in error-checking, or potentially unsafe in some way. java , and the compiler will give you more verbose information as to what exactly is causing the error.

To compile with -Xlint:unchecked in IntelliJ IDEA:

1. Go to Settings dialog ( Ctrl + Alt + S or ⌘ + , )
2. Select Compiler > Java Compiler.
3. Add following into the field Additional command line parameters : -Xlint:unchecked.
4. Run your compile again.

If we can’t eliminate the “unchecked cast” warning and we’re sure that the code provoking the warning is typesafe, we can suppress the warning using the SuppressWarnings(“unchecked”) annotation. When we use the @SuppressWarning(“unchecked”) annotation, we should always put it on the smallest scope possible.

Uwe Schindler: Unsafe is an private and internal class of the Oracle JDK / OpenJDK platform. It’s used behind the scenes in a lot of public Java APIs to implement operations which are otherwise only available with native C or assembly code.

Unchecked cast means that you are (implicitly or explicitly) casting from a generic type to a nonqualified type or the other way around.

Your best option would be to fix the use of deprecated APIs. However, an option would be to add the @SuppressWarnings(“deprecation”) annotation to the classes or methods that are using the deprecated APIs. For Jdk 5, I use -Xlint:all . This appears to suppress all the warnings of deprecation, unchecked, etc.

An unchecked warning tells a programmer that a cast may cause a program to throw an exception somewhere else. Suppressing the warning with @SuppressWarnings(“unchecked”) tells the compiler that the programmer believes the code to be safe and won’t cause unexpected exceptions.

Use of @SuppressWarnings is to suppress or ignore warnings coming from the compiler, i.e., the compiler will ignore warnings if any for that piece of code.

What causes Java uses unchecked or unsafe operations? With Java, if you compile code that the compiler believes to be poor in error checking or hazardous in some way, the message Java uses unchecked or unsafe operations will appear. In fact, it’s a warning rather than an error, and luckily, it won’t stop you from building the code.

If you want to know about unchecked or unsafe operations, you can use below command: Note: PrintArrayListMain.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. How to resolve warning message: uses unchecked or unsafe operations. You can resolve this warning message by using generics with Collections.

uses unchecked or unsafe operations is displayed when you compile code which compiler considers to be lacking in error checking or unsafe in some way. It’s a warning, not an error, and will not prevent you from compiling the code.

So what you can do is put a flag in your code that does the same thing. The line just above the class signature will tell JavaC to not display any unchecked warnings from within the class. You also can use the same @SuppressWarnings (“unchecked”) above method signatures if you only want to ignore the check in specific methods.