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

Support Object in visit API #54

Merged
merged 5 commits into from
Mar 26, 2019
Merged

Support Object in visit API #54

merged 5 commits into from
Mar 26, 2019

Conversation

jroesch
Copy link
Member

@jroesch jroesch commented Mar 26, 2019

This is part of the work in apache/tvm#2889, working on cleaning both up this will have to merge first in order to compile the other PR.

@@ -23,6 +23,12 @@ namespace runtime {
class NDArray;
} // namespace runtime

namespace relay {
namespace vm {
Copy link
Member

@tqchen tqchen Mar 26, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps make it runtime::vm::VMObject? The runtime namespace is isolated and can be compiled separately(in AOT)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was planning to rename right now, to simply the organization, just pushed a commit.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is VMObject a reference class(like NDArray) or the container itself? Ideally we want it to be the reference class

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could likely be merged into the namspace above(runtime::NDArray)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a reference class, we can move into runtime if you want

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can make the decison. Perhaps it makes sense to move to runtime given that there is no other runtime Object

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, not sure if we should keep it isolated or not. Maybe it makes sense if we will reuse for AoT/JiT, etc.

@@ -41,6 +46,7 @@ class EXPORT AttrVisitor {
virtual void Visit(const char* key, Type* value) = 0;
virtual void Visit(const char* key, NodeRef* value) = 0;
virtual void Visit(const char* key, runtime::NDArray* value) = 0;
virtual void Visit(const char* key, runtime::vm::Object* value) = 0;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let us just do runtime::Object then

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just decided right before you posted this ha. Just pushed a commit to do so.

@tqchen tqchen merged commit 92ef20f into dmlc:master Mar 26, 2019
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.

2 participants