Skip to content
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

[Node] Allow Array/Map store objects that are not NodeRef #4430

Merged
merged 1 commit into from
Nov 26, 2019
Merged

[Node] Allow Array/Map store objects that are not NodeRef #4430

merged 1 commit into from
Nov 26, 2019

Conversation

junrushao
Copy link
Member

@tqchen @icemelon9 Please review :-)

@zhiics
Copy link
Member

zhiics commented Nov 26, 2019

@junrushao1994 Just out of curiosity, it looks that this will allow us to return runtime object refs like modules. Is this what you need? @tqchen do we want to move container.h under runtime at some point?

@junrushao
Copy link
Member Author

@zhiics You are right. Array/Map/StrMap are designed to allow storing all possible objects.

do we want to move container.h under runtime at some point?

I personally think that this could happen after we have containers with POD C ABI

@junrushao
Copy link
Member Author

@tqchen @zhiics shall we merge this in? Thanks!

@tqchen tqchen merged commit e35ecae into apache:master Nov 26, 2019
leo-blonk pushed a commit to leo-blonk/tvm that referenced this pull request Nov 29, 2019
zxy844288792 pushed a commit to zxy844288792/tvm that referenced this pull request Dec 13, 2019
zxy844288792 pushed a commit to neo-ai/tvm that referenced this pull request Dec 13, 2019
@junrushao junrushao deleted the container-object branch January 6, 2022 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants