spec: prepare for variables and parameters #47
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary ======= * subdivide expressions into l-value and r-value expressions * add definitions for values, locations, and cells * introduce the notion of linear, affine, and normal types Details ======= Some definitions and terminology was missing to be able to describe / specify the semantics of variables and assignments. This commit aims to extend the specification with the necessary bits. As a preparation for future resource management, linear and affine types are introduced already, though they're not of practical relevance yet.
zerbina
commented
Sep 26, 2024
saem
approved these changes
Sep 27, 2024
"object" is also not ideal, but it's a bit better than "value" and should do for now.
|
@saem: I've replaced the relevant mentions of
|
saem
approved these changes
Sep 28, 2024
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Details
Some definitions and terminology was missing to be able to describe /
specify the semantics of variables and assignments. This commit aims to
extend the specification with the necessary parts.
As a preparation for future resource management, linear and affine
types are introduced already, though they're not of practical relevance
yet.
Notes For Reviewers
Ifexpression support #46 is mergedOverall, I'm not too happy with the current specification. I think it's not formal enough, and the way it's currently structured is also off. It'll need a redo, eventually.