Ivano Pagano

Change the behaviour of non-group predicates being OR-ed with named groups

5

Relates to #516 The current solution considers predicates with no explicit `group` as being part of a default anonymous group, hence they're always combined with other, named, groups using "OR"...

Block operations which include some code (like transactions) have a representation in conseil both in its original micheline format (as read from the tezos chain) and in converted michelson format,...

We currently have a minor inconsistency in how methods are called in the `TezosDatabaseOperations`. There are generic `write`, more specific `insert` and `upsert`. We might want to establish a naming...

In order to make the core logic of Conseil more readable, the code should be refactored so the core is a small composition of multiple obviously-understandable functions.

Currently we don't have a detailed logging trace of the elements that are fetched and stored by Lorre, as the batched fetchers hides that level of detail, which would be...

Typeclass inheritance syntax proposal

2

in the [type classes doc](https://github.com/LukaJCB/typeclass-proposal/blob/master/docs/typeclasses.md#type-class-requirements-inheritance) you suggest using the following syntax to imply type class "requirements", which introduces a previously unused notation: ```scala type class Monoid[A] : Semigroup[A] { def...