V0.2 backend dynamic node support#172
Merged
Merged
Conversation
…com/chaosddp/maro into v0.2_backend_dynamic_enum_attr_type
Jinyu-W
suggested changes
Dec 29, 2020
Jinyu-W
approved these changes
Jan 22, 2021
20 tasks
This file contains hidden or 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
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.
Description
Main changes:
use an enum like class to specified attribute,
support more attribute data type for both 2 backends.
use a simple string template to generate dup codes before compiling.
a backend write with c++ to support dynamic attributes
add 2 attribute parameters,
const: same as normal, but not copied into snapshot list, can be queried even without snapshot taking (must specified a tick for padding)
list: dynamic length attribute, support remove, append, clear, resize and slice accessing.
An attribute cannot both be const and list, it will cause an error.
# Linked issue(s)/Pull request(s)
#109
#110
#141
Type of Change
Related Component
Has Been Tested
Needs Follow Up Actions
Checklist