LiquidJava is an additional type checker for Java, based on liquid types and typestates, which provides additional safety guarantees to Java programs through refinements at compile time.
To refine a variable, field, parameter or return value, use the @Refinement annotation with a predicate as an argument. The predicate must be a boolean expression that uses the name of the variable being refined (or _) to refer to its value.
@Refinement("a > 0")
int a = 3;
a = -8; // Refinement Error
@Refinement("_ >= low && _ <= high")
public static int midpoint(
@Refinement("_ <= high") int low,
int high
) {
return low + (high - low) / 2;
}
midpoint(5, 10);
midpoint(10, 5); // Refinement ErrorLiquidJava also supports object state modeling via typestates, which allows enforcing protocols on objects using the @StateSet and @StateRefinement annotations. The @StateSet annotation defines the possible states of an object, while the @StateRefinement annotation specifies the allowed transitions between states for each method. The @ExternalRefinementsFor annotation is used to specify an external class for which the refinements are being defined.
@ExternalRefinementsFor("java.net.Socket")
@StateSet({"unconnected", "bound", "connected", "closed"})
public interface SocketRefinements {
@StateRefinement(to="unconnected(this)")
public void Socket();
@StateRefinement(from="unconnected(this)", to="bound(this)")
public void bind(SocketAddress add);
@StateRefinement(from="bound(this)", to="connected(this)")
public void connect(SocketAddress add);
@StateRefinement(from="connected(this)")
public void sendUrgentData(int n);
@StateRefinement(from="!closed(this)", to="closed(this)")
public void close();
}
Socket socket = new Socket();
socket.bind(new InetSocketAddress("localhost", 8080));
socket.sendUrgentData(1); // State Refinement Error
socket.close();Finally, LiquidJava also provides ghost variables that are used to track additional information about the program state with the @Ghost annotation. These are also updated through the @StateRefinement annotation.
@ExternalRefinementsFor("java.util.Stack")
@Ghost("int size")
public interface StackRefinements<E> {
@StateRefinement(to="size(this) == 0")
public void Stack();
@StateRefinement(to="size(this) == size(old(this)) + 1")
public E push(E elem);
@StateRefinement(from="size(this) > 0", to="size(this) == size(old(this)) - 1")
public E pop();
@StateRefinement(from="size(this) > 0")
public E peek();
}
Stack<Integer> stack = new Stack<>();
stack.push(1);
stack.pop();
stack.pop(); // State Refinement ErrorThe easiest way to use LiquidJava is through its VS Code extension, which uses the LiquidJava verifier directly inside VS Code, with real-time error diagnostics and syntax highlighting for refinements.
For development, you may use the LiquidJava verifier from the command line.
Before setting up LiquidJava, ensure you have the following installed:
- Java 20+ - JDK for compiling and running Java programs
- Maven 3.6+ - For building and dependency management
Additionally, you'll need the following dependency, which includes the LiquidJava API annotations:
<dependency>
<groupId>io.github.liquid-java</groupId>
<artifactId>liquidjava-api</artifactId>
<version>0.0.7</version>
</dependency>repositories {
mavenCentral()
}
dependencies {
implementation 'io.github.liquid-java:liquidjava-api:0.0.7'
}- Clone the repository:
git clone https://github.com/liquid-java/liquidjava.git - Build the project
mvn clean install - Run tests to verify installation:
mvn test - If importing into an IDE, import the project as a Maven project using the root
pom.xml
To run LiquidJava, use the Maven command below, replacing /path/to/your/project with the path to the Java file or directory you want to verify.
mvn exec:java -pl liquidjava-verifier -Dexec.mainClass="liquidjava.api.CommandLineLauncher" -Dexec.args="/path/to/your/project"If you're on Linux/macOS, you can use the liquidjava script (from the repository root) to simplify the process.
The script recompiles the verifier only when local sources or Maven files have changed.
The LiquidJava verifier can be run from the command line with the following options:
| Option | Description |
|---|---|
<...paths> |
Paths (files or directories) to be verified by LiquidJava |
-h, --help |
Show the help message with available options |
-v, --version |
Show the current version of the verifier |
-d, --debug |
Enable debug logging and skip expression simplification for troubleshooting |
-lsp, --language-server |
Enable language server mode for editor support |
Test a correct case:
./liquidjava liquidjava-example/src/main/java/testSuite/CorrectSimpleAssignment.javaThis should output: Correct! Passed Verification.
Test an error case:
./liquidjava liquidjava-example/src/main/java/testSuite/ErrorSimpleAssignment.javaThis should output an error message describing the refinement violation.
Run ./mvnw test to run all the tests in LiquidJava.
The TestExamples.java test runs the Java files and test directories under the testSuite directory in liquidjava-example.
Test inputs are discovered as follows:
- Top-level Java files are treated as individual test inputs
- Leaf directories are treated as a single test input
Test results are determined by inline diagnostic expectations using comments:
value = -1; // Expect: Refinement ErrorEach expected diagnostic must be reported, and every reported error or warning must have a corresponding expectation. Tests with no expectation must produce no diagnostics.
- docs: Contains documents used for the design of the language. This folder includes a README with the link to the full artifact used in the design process. It also contains initial documents used to prepare the design of the refinements language during its evaluation
- liquidjava-api: Includes the annotations that can be introduced in the Java programs to add the refinements
- liquidjava-example: Includes some examples and the test suite used for testing the verifier
- liquidjava-verifier: Includes the implementation of the verifier. Its main packages are:
api: Includes theCommandLineLauncher, which verifies one or more specified files or directoriesdiagnostics: Reports verification errors and warningsprocessor: Handles the type checkingrj_language: Parses refinement strings and contains the Refinements Language (RJ) ASTsmt: Translates verification conditions to the SMT solver and processes its resultsutils: Provides shared utility classes
You can find out more about LiquidJava in the following resources:
