-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v0.9.0-alpha.1] feat: top level variable back reference #1104
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
Peefy
added
runtime
Issues or PRs related to kcl runtime including value and value opertions
codegen
labels
Mar 4, 2024
Peefy
force-pushed
the
top-level-var-back-reference
branch
5 times, most recently
from
March 6, 2024 09:48
f2c8efd
to
c67699d
Compare
Peefy
changed the title
[WIP] feat: top level variable back reference
[WIP v0.9-alpha.1] feat: top level variable back reference
Mar 7, 2024
Peefy
force-pushed
the
top-level-var-back-reference
branch
from
March 7, 2024 08:15
c67699d
to
598ebd6
Compare
Pull Request Test Coverage Report for Build 9000600409Details
💛 - Coveralls |
16 tasks
Peefy
force-pushed
the
top-level-var-back-reference
branch
from
March 8, 2024 06:01
598ebd6
to
29f4b43
Compare
Peefy
force-pushed
the
top-level-var-back-reference
branch
3 times, most recently
from
March 22, 2024 13:44
5f0bb85
to
fe7d248
Compare
Peefy
force-pushed
the
top-level-var-back-reference
branch
3 times, most recently
from
May 6, 2024 08:39
5a3cbe8
to
325d4d8
Compare
Peefy
changed the title
[WIP v0.9-alpha.1] feat: top level variable back reference
[v0.9.0-alpha.1] feat: top level variable back reference
May 6, 2024
Peefy
force-pushed
the
top-level-var-back-reference
branch
3 times, most recently
from
May 6, 2024 10:17
4aa4b17
to
656b120
Compare
Peefy
force-pushed
the
top-level-var-back-reference
branch
9 times, most recently
from
May 7, 2024 08:55
ac45220
to
5069c1e
Compare
Signed-off-by: peefy <xpf6677@163.com>
Signed-off-by: peefy <xpf6677@163.com>
Signed-off-by: peefy <xpf6677@163.com>
Peefy
force-pushed
the
top-level-var-back-reference
branch
from
May 8, 2024 10:53
d4910de
to
6132e8d
Compare
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.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
Closes #247
Closes kcl-lang/kpm#241
Closes #1176
Closes #1253
feat: top level variable back reference
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: