Luca Negrini

**Description** Most programming languages have constructs to define code blocks to catch and handle runtime errors. There is currently no way to define these in cfgs.

**Description** The abstract state should have capabilities to express error tokens/exceptions. An example for this is when the type analysis discovers that there is a possible cast error: fixpoint algorithms...

**Description** A statement could terminate execution immediately (i.e. Java's `System.exit(exitCode)`). We should add a way to support this in the fixpoint iteration.

**Description** LiSA should provide native support for generic types, such as `List`.

**Description** At some point we should move to java 17, with records and pattern matching. We should also modularize the project.

**Description** `LiSAFactory.configurableComponents()` can return a list of concrete implementation of the analysis components that can be configured. This, as well as information about options inside `LiSAConfiguration`, should end up in...

**Description** Option for generating mockups of each compilation unit that can redefine all methods returning top to simulate external instances (i.e. application behaves as a library that can be extended)....

**Description** Partial (or incremental) analyses should fit into LiSA capabilities. (probably blocked by #121)

**Description** Make the fix-point algorithm parametric with loop unrolling.

**Description** IMP should be equipped with a concrete interpreter and a "collecting" one, that help showcasing the differences between concrete and abstract world and why it isn't possible to just...