Why consider using Guava-like Libraries for API Contract Conditions Checks

This article represents a perspective on why one should consider using Pre/Post condition checks libraries rather than writing it down time and again in their code.

While doing code reviews, many a times, I have found people using preconditions checks such as “Not Null” in a casual manner rather than based on API contracts requiring pre and post conditions checks. Such checks, at times,  do make code difficult to read, learn or understand. One may want to rather use home-grown or external (proven ones) libraries for doing such checks. Not only does it enhance code readability and learn-ability but also, it does make you aware of contracts you put in the code thereby including only necessary checks and, hence, cleaner code.

Consider code snippets such as following:

//
// In traditional manner
//

Above considers some of the popular libraries which are mentioned below:

• Java Libraries vis-a-vis API
  • Google Guava – Preconditions
  • Spring framework – Assert
  • Apache Commons – Validate
• .NET framework vis-a-vis API
  • Code Contracts – Contract

1. Check for validation of methods’ arguments.  Throws exception such as IllegalArgumantException or the equivalent upon failure.
2. Check whether a specific value is not null.  Throws exception such as NullPointerException or the equivalent upon failure.
3. Check state of the object.  Throws exception such as IllegalStateException or the equivalent upon failure
4. Check whether the index is a valid element or position index into a list, string, or array with the specified size. An element index may range from 0 inclusive to size exclusive. Throws exception such as IndexOutOfBoundsException or the equivalent upon failure