From 75a0f8b6f95edc49e7071bfab09ba5f7a8c0b7eb Mon Sep 17 00:00:00 2001 From: Lakshya A Agrawal Date: Tue, 21 Nov 2023 19:45:21 +0530 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d927dec..fc81cb5 100644 --- a/README.md +++ b/README.md @@ -188,7 +188,7 @@ A monitor under the Monitor-Guided Decoding framework, is instantiated using `mu #### Monitor for valid number of arguments to function calls [src/monitors4codegen/monitor_guided_decoding/monitors/numargs_monitor.py](src/monitors4codegen/monitor_guided_decoding/monitors/numargs_monitor.py) provides the instantiation of `Monitor` class for numargs_monitor. It can be used to guide LMs to generate correct number of arguments to function calls. Unit tests, which also provide usage examples are present in [tests/monitor_guided_decoding/test_numargs_monitor_java.py](tests/monitor_guided_decoding/test_numargs_monitor_java.py). -### Monitor for typestate specifications +#### Monitor for typestate specifications The typestate analysis is used to enforce that methods on an object are called in a certain order, consistent with the ordering constraints provided by the API contracts. Example usage of the typestate monitor for Rust is available in the unit test file [tests/monitor_guided_decoding/test_typestate_monitor_rust.py](tests/monitor_guided_decoding/test_typestate_monitor_rust.py). #### Switch-Enum Monitor