Re: [apache/tvm-rfcs] [RFC] TVMScript Metaprogramming (PR #79)

2022-07-28 Thread Junru Shao
To follow up with our latest discussion with @tkonolige @areusch @csullivan @jwfromm et al. The following questions are raised in our discussion: 1. Move discussion of vendor IR to tradeoffs / benefits section rather than core motivation. 2. (Section 2) Parser registration example is a little co

Re: [apache/tvm-rfcs] [RFC] TVMScript Metaprogramming (PR #79)

2022-07-28 Thread Steven S. Lyubomirsky
Could you give an example of the metaprogramming? E.g., one of creating some value in ordinary Python and then referencing it from TVMScript -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/79#issuecomment-1198590164 You are receiving this because you

Re: [apache/tvm-rfcs] [RFC] TVMScript Metaprogramming (PR #79)

2022-07-28 Thread Junru Shao
@slyubomirsky Sure! Please see F1 and F2 for existing meta-programming capability (https://github.com/yelite/tvm-rfcs/blob/tvmscript-metaprogramming/rfcs/0079-tvmscript-metaprogramming.md#f1-template-metaprogramming), and see F4 for interleaving python interpreter with the parser. The quotation

Re: [apache/tvm-rfcs] [RFC] TVMScript Metaprogramming (PR #79)

2022-07-28 Thread Steven S. Lyubomirsky
So if you define a variable in a quoted portion, you should be able to reference it in the quoted portion? -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/79#issuecomment-1198624317 You are receiving this because you are subscribed to this thread. M

Re: [apache/tvm-rfcs] [RFC] TVMScript Metaprogramming (PR #79)

2022-07-28 Thread Junru Shao
> So if you define a variable in a quoted portion, you should be able to > reference it in the unquoted portion - From quoted to unquoted: Yes, that's correct. - From unquoted to quoted: For security concern, accessing values from unquoted portion will require explicit specification if the values