Some design notes for the Rust-lite semantics #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These notes are not meant to describe the definite version of the Rust-lite semantics, especially for the execution part, which is obviously incomplete, and whose configuration is just a sketch (although it may be a fairly good one).
However, these notes are meant to describe what I intended to do for this semantics, and the intent of this PR is to get approval for the direction in which this semantics will go.
These notes are out of sync with the current implementation of "indexing", which should have been called "preprocessing" anyway. I plan to fix that, unless I should change focus to a different semantics (e.g. Solidity-lite).