Draft: Contracts : force storage type definition
Motivation and Context
This force a contract (i.e. a program with at least one [@entry] declaration) to define a type "storage".
benefits:
- any code transformation on contracts before typing will be easier because you can refer to the storage type using a variable (dynamic entries)
Description
A contract (i.e. a program with at least one [@entry] declaration) must define storage type.
Component
-
compiler -
website -
webide -
vscode-plugin -
debugger
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to not work as expected) -
Performance improvement (non-breaking change that improves performance) -
None (change with no changelog)
Changelog
A contract (i.e. a program with at least one [@entry] declaration) must define storage type.
Checklist:
-
If a new syntax has been introduced, put a message on slack ligo-lsp -
Changes follow the existing coding style (use dune @fmt
to check). -
Tests for the changes have been added (for bug fixes / feature). -
Documentation has been updated. -
Changelog description has been added (if appropriate). -
Start titles under ## Changelog
section with #### (if appropriate). -
There is no image or uploaded file in changelog -
Examples in changed behaviour have been added to the changelog (for breaking change / feature).
Edited by Rémi