-
Notifications
You must be signed in to change notification settings - Fork 45
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 for subfunctions included in a subgraphs #41
Conversation
Signed-off-by: xadupre <xadupre@microsoft.com>
|
||
@script(opset) | ||
@script(CustomOpset('this', 1)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any significance to this change? If I am not mistaken, CustomOpset
is mutable, with methods to add new functions to it. In principle, we could potentially update the opset object in script
.
I think this does not matter right now, but I feel it may be useful to have examples share the same opset object in the long run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No significance except the converter failed. We should decide how to handle global variables, ignore them, or do something else. Ignore them is easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am surprised. Are you saying it fails with
opset = CustomOpset('this', 1)
@script(opset)
but succeeds with
@script(CustomOpset('this', 1))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
Signed-off-by: xadupre <xadupre@microsoft.com>
Signed-off-by: xadupre <xadupre@microsoft.com>
Signed-off-by: xadupre <xadupre@microsoft.com>
Signed-off-by: xadupre <xadupre@microsoft.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will create an issue about the point I was making in our call (about having a well-defined spec about the functions that will be included in a created ModelProto, and one that allows users to control it). The issue can be addressed in a separate PR.
Signed-off-by: xadupre xadupre@microsoft.com