by

Reudismam Rolim, Federal University of Campina Grande, Brazil

Loris D’Antoni, University of Wisconsin-Madison, USA

Gustavo Soares, Microsoft Research, USA

Rohit Gheyi, Federal University of Campina Grande, Brazil

We built a tool, Revisar, that automatically learns useful code edits in Java using revision histories. Given code repositories as input, Revisar works as follows:

1) It picks every edit of the across multiple repositories;

2) It groups similar edits using some fancy technique;

3) It generalizes the edits in transformations that can be applied to code.

All transformations we discovered can be found here, but, in this post, we present some of the most common and cool code transformations by Java developers that Revisar automatically discovered!

More information about Revisar can be found in this paper.

String to Character

In Java, we can represent a character both as a string or a character. For some operations such as concatenating or appending a value to a StringBuilder , it is better to represent the value as a character if the value itself is a character. Representing the value as a character improves performance. For instance, this string to character edit in the Guava project improved performance by 10-25%. This transformation is included in the catalog of anomalies of tools such as PMD.

public class Foo { void bar () { StringBuffer sb = new StringBuffer (); // Avoid this sb . append ( "a" ); // use instead something like this StringBuffer sb = new StringBuffer (); sb . append ( 'a' ); } }

StringBuffer to StringBuilder

StringBuffer and StringBuilder denote a mutable sequence of characters. These two types are compatible, but StringBuilder provides no guarantee of synchronization. Since synchronization is rarely used, StringBuilder offers better performance over its counterpart and is recommended by Java. Code snippet below shows an example of the use of the StringBuilder class.

public class Bar { public void foo () { StringBuffer a = new StringBuffer (); //In a single thread, prefer the following: StringBuilder b = new StringBuilder (); } }

Use Collection isEmpty

The use of isEmpty is recommended to verify whether the list contains no elements instead of verifying the size of a collection. Although in the majority of collections, these two constructions are equivalent, for other collections computing the size of an arbitrary list could be expensive. For instance, in the class ConcurrentSkipListSet, the size method is not a constant-time operation. This transformation is included in the catalog of anomalies of tools such as PMD. Code snippet below shows an example of the use of the isEmpty method.

public class Foo { void good () { List foo = getList (); if ( foo . isEmpty ()) { // blah } } void bad () { List foo = getList (); if ( foo . size () == 0 ) { // blah } } }

Prefer String Literal equals Method

The equals method is widely used. Some uses can cause NullPointerException due to the right-hand side of the method object reference being null. When using the equals method to compare some variable to a string literal, developers could overcome null pointer exceptions by allowing the string literal to call the equals method because a string literal is never null. Since Java string literal equals method checks for null, we do not need to check for null explicitly when calling the equals method of a string literal.

public class Foo { //Good void good ( String str ) { if ( "string" . equals ( str )) { // blah } } // Causes error if str is null void bad ( String str ) { if ( str . equals ( "string" ) { // blah } } // Do not need to check for null since equals evaluate it. void bad2 ( String str ) { if ( str != null && str . equals ( "string" ) { // blah } } }

Use valueOf instead Wrapper Constructor

Java allows using the method valueOf or the constructor to create wrapper objects of primitive types. Java recommends the use of valueOf for better performance since valueOf method caches some values. This checker is included in the catalog of anomalies of tools such as Sonar. Code snippet below shows an example of the use of the valueOf method.

Integer a = new Integer ( 1 ); //Instead of using the Integer constructor, use the valueOf Integer b = Integer . valueOf ( 1 );

Avoid instances of FileInputStream/FileOutputStream

FileInputStream and FileOutputStream override finalize() . As a result, objects of these classes go to a category that is removed only when a full cleaning is performed by the Garbage Collector. Since Java 7, developers can use Files.new to improve program performance. This anomaly is described as a bug by Java JDK.

//Bad public void writeToFile ( String fileName , byte [] content ) throws IOException { try ( FileOutputStream os = new FileOutputStream ( fileName )) { os . write ( content ); } } //Good public void writeToFile ( String fileName , byte [] content ) throws IOException { try ( OutputStream os = Files . newOutputStream ( Paths . get ( fileName ))) { os . write ( content ); } }

Field, Parameter, Local Variable Could Be Final

Besides classes and methods, developers can use the final modifier in fields, parameters, and local variables. The meaning differs for each one of these uses. A final class cannot be extended, a final method cannot be overridden, and final fields, parameters, and local variables cannot change their value. Thus, a final modifier ensures that fields, parameters, and local variables cannot be re-assigned. A re-assignment generates an error at compile-time. Final modifier improves clarity, helps developers to debug their code showing Java constructions that change state and are more likely to break the code. In addition, final modifier allows the compiler and virtual machine to optimize the code. This anomaly is included in tools such as PMD. In addition, IDEs such as Eclipse and NetBeans can be configured to add final modifiers to fields, parameters, and local variables automatically on saving. Code snippet below shows an example of adding the final modifier to a parameter. Variable a is assigned a single time. Thus, it can be declared final such as variable b .

public class Bar { public void foo () { String a = "a" ; //if a is not assigned again it is better to do this: final String b = "b" ; }

Allows Type Inference for Generic Instance Creation

Since Java 7, developers can replace the type parameters required to invoke the constructor of a generic class with an empty set of type parameters (<>). The empty set of type parameters, also known as diamond, allows the compiler to infer type parameters from the context. By using diamond construction, developers clarify the use of generic instead of the deprecated raw types, the version of a generic type without type parameters. Java allows raw types only to ensure compatibility with pre-generics code. The benefit of the diamond constructor, in this context, is clarity since it is more concise. Code snippet below shows the use of the diamond operator in a variable declaration. Instead of using the type parameter <String, List<String>> , developers can use the diamond to invoke the constructor of the generic HashMap class.

//Bad Map < String , List < String >> myMap = new HashMap < String , List < String >>(); //Good Map < String , List < String >> myMap = new HashMap <>();

Remove Raw Type

Java discourages the use of raw types. A raw type denotes a generic type without type parameters, which was used in the outdated version of Java and is allowed to ensure compatibility with pre-generics code. Since type parameters of raw types are unchecked, they can cause errors at run-time. The Java compiler generates a warning to indicate the use of raw types into the source code. Code snippet below shows the use of a raw type. Developers can pass any type of collection to the constructor of a raw type since it is unchecked.

List < String > strings = ... // some list that contains some strings // Totally legal since you used the raw type and lost all type checking! List < Integer > integers = new LinkedList ( strings ); // Not legal since the right side is actually generic! List < Integer > integers = new LinkedList <>( strings );

Prefer Class<?>

Java prefers Class<?> over plain Class although these constructions are equivalent. The benefit of Class<?> is clarity since developers explicitly indicate that they are aware of not using an outdated Java construction. The Java compiler generates a warning on the use of Class . Code snippet below exemplifies the use of Class<?> .

//Any class Class anyType = String . class ; //Unknown Type Class <?> unknownType = String . class ;

Use Variadic Functions

Variadic functions denote functions that use variable-length arguments (varargs). This feature was introduced in Java 5 to indicate that the method receives zero or more arguments. Prior to Java 5, if a method receives a variable number of arguments, developers have to create overload method for each number of arguments or to pass an array of arguments to the method. The benefit of using varargs is simplicity since developers do not need to create overload methods and use the same notation independently of the number of arguments. From the compiler’s perspective, the method receives an array as the parameter. Code snippet below shows the use of the Variadic functions.

//... myMethod ( "foo" , "bar" ); myMethod ( "foo" , "bar" , "baz" ); myMethod ( new String [] { "foo" , "var" , "baz" }); // you can even pass an array //... public void myMethod ( String ... strings ) { for ( String whatever: strings ) { // do what ever you want } // the code above is equivalent to for ( int i = 0 ; i < strings . length ; i ++) { // classical for. In this case you use strings[i] } }

References