Georgiy Komarov

Results 50 issues of Georgiy Komarov

It would be useful to have a CLI option that allows the user to prohibit the execution of certain static analyses. This will allow us to have much more analyses...

enhancement
performance
static analysis

Anonymous records in constructors would help remembering the meanings of AST node components and also with standardizing the naming scheme of AST node components. Here is an example: https://github.com/mtt-lang/mtt-lang/blob/master/core/Ast.ml#L37 Probably,...

enhancement
good first issue
code style / refactoring

The `ScillaIdentifier` module is often used as a key of `Map` and `Set` collections, so it must implement functions defined in the `Comparable` functor. Because of this we create an...

enhancement
code style / refactoring

The dead code analyzer could be improved to support recursive definitions like these: ```ocaml transition tr4 ( x : ByStr20 with contract field y : ByStr20 with contract field unused...

enhancement
static analysis
dead-code-detector

We could use `Cmdliner` instead of [the manual parsing of CLI argument](https://github.com/Zilliqa/scilla/blob/55f1b64dba4db9096acea243e0e71aaa3029d3aa/src/base/RunnerUtil.ml#L207). This will allow us to: + Add parametrized options more easily. + Generate `man` pages automatically. Here is...

enhancement
good first issue
usability

Folding through nested statements and expressions is a common pattern used almost in every static analysis. However, this pattern is too verbose and error-prone, because a developer could forget to...

enhancement
code style / refactoring

This PR adds `tooltip` attribute for graph, edges and nodes. Reference: https://graphviz.org/docs/attrs/tooltip/.

The current implementation of the test suite in Python seems too complicated. It could be rewritten in OCaml using cram tests and alcotest/ounit2.

enhancement
test

We should set maximum supported versions of dependencies in `dune-project` to avoid backward compatibilities problems in the future.

enhancement
good first issue

The following snippet raises false positive for CP1: ``` PROGRAM l10 VAR END_VAR %MW10.2.4.1 := 42; (* False positive PLCOPEN-CP1 *) END_PROGRAM ``` Actually, this warning should be reported only...

bug