AndrewZhaoLuo commented on pull request #10852: URL: https://github.com/apache/tvm/pull/10852#issuecomment-1085188581
I thought about this and I think that's a little tougher. I believe the way deserialization works (a lot of this is kind of assumed lol, I should probably double check) is it just sets the states of underlying node and doesn't go through otherwise normal constructor. I don't want to change this framework. We can probably expose a method that does what you describe but then the user when deserializing will need to invoke this method again which I feel is more error prone. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
