We always need the original syntax to enable bidirectional property. It does
not hurt though to enable sugars that allows us to have a combination on top.
How about we start with the original syntax and then discuss sugar as a
separate topic
--
Reply to this email directly or view it on GitHub
reuse T.alloc_buffer seems good，as long as there is no ambiguity for parser
impl ：）
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/70#issuecomment-1149935097
You are receiving this because you are subscribed to this thread.
Message ID:
Please join us in welcoming @tkonolige as a new committer to TVM! Tristan has
been consistently contributing to all parts of TVM, from the runtimes to the
frontends, schedulers, tuning, documentation, CI and general bug fixing.
Notably, he contributed libbacktrace and PAPI support.
- [Commits
Well deserved! Congrats Tristan!
---
[Visit
Topic](https://discuss.tvm.apache.org/t/community-tristan-konolige-committer/12933/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/email
@areusch @Hzfengsy I've updated the RFC. It is ready for another look
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/70#issuecomment-1150342730
You are receiving this because you are subscribed to this thread.
Message ID:
very sorry for the delay here.
@junrushao1994 i guess i'm still a little fuzzy on the rationale for why we
want to have two ways to parse TVMScript. I know this is a bit bigger than just
this RFC, but with this RFC we're further pushing the cart down this path so
I'd like us to be explicit abou
> Relay has a single roundtrippable serialization format, as do most languages.
> I think we benefit from this in that we only have one set of tests to
> maintain.
To clarify, Relay has two roundtrippable serialization formats: text format and
json. people use text format for readability, and i
