Loci helps the programmer to identify unintended (& intended too) leaks of thread local data during compile time.
We pronounce Loci like: /lɒkiː/
We are trying our very best to make Loci as simple as possible, that is how it extends Java with only e annotations, namely (
Loci can help you find as much leaks as possible during the compile time, however if you don't apply it properly it can sometimes fail to find proper bugs.
Please refer to here.
We believe in sharing, the more programmer use Loci the more solid it can get.
Indeed, Loci is an optional type checker, which has zero affect on your program's runtime behavior, all it does is some "additional" compile time check.
Indeed, you don't need Loci to run your already annotated programs. Loci is only needed during compile time.
The best way to help Loci, is by using it and trying to find(& report) as much bugs as possible, here you can report bugs.
Short answer, No. But we are working on it, please report a bug if you found a bad annotated class.
You can get the Loci source code, by either downloading the latest distributed source code here or the latest drafts from the repository. We are using Subversion as our version control, to obtain the source code do the following:
$ svn co https://svn.java.net/svn/loci~main main
for more information, refer to this page.
No, Loci is not needed during the run time, therefore you are free to use it for you non-GPL programs.