quic-sanirudh commented on PR #11225: URL: https://github.com/apache/tvm/pull/11225#issuecomment-1119688463
@Lunderberg @vinx13 This is great, thanks a lot, I would love to start using this. I do have a small doubt however. Is there a reason why we're introducing a new schedule primitive instead of allowing the user to pass something similar to `te.AXIS_SEPARATOR` to layout_transform and internally call both `ScheduleTransformLayout` and `SetAxisSeparator` as done for te? The reason for this question is that I discussed once with Eric, but again, the list to be passed to axis_separators argument seems like an internal detail and might confuse users. Also it might make it difficult for us to modify how axis_separators are handled internally later if needed once we expose this detail into user facing API. -- 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]
