Thanks @comaniac. It would be great if people can discuss a bit more in terms of API choices. I think we achieved the proposed goals.
Specifically, here are some "complains" I have by quickly looking into the API: - select.py was a bit confusing(it reminds me of select API of socket networking, but it is not?) - It is more like a annotation API that annotates the tasks, can we treat it as a pass over the set of tasks(if that is what we want - The depend field in the autotvm should be documented, and we need to think about a better name (Seems the current specified behavior is to stop tuning x) and make use of dependent data I do not have time too think too deep into this. but perhaps others can do a review and discuss the possible candidates? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/dmlc/tvm/issues/4188#issuecomment-548005028
