[truffle] depend on JVM backend?

[tisonkun]

@pmurias currently our truffle backend rely on JVM backend, I wonder if this is necessary and if not, what is the plan build NQP directly on truffle framework; if so, does it mean that truffle backend is constrained by JVM backend(both use case and performance).

To sum up, is there a draft of truffle backend design document?

Thanks for your effort!

[pmurias]

Truffle using the JVM backend is temporary. The plan is to migrate to using just truffle when the truffle backend can compile and run NQP itself

…

On Wed, 12 Sep 2018 at 07:19, 陈梓立 ***@***.***> wrote: @pmurias <https://github.com/pmurias> currently our truffle backend rely on JVM backend, I wonder if this is necessary and if not, what is the plan build NQP directly on truffle framework; if so, does it mean that truffle backend is constrained by JVM backend(both use case and performance). To sum up, is there a draft of truffle backend design document? Thanks for your effort! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#500>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGXpsWLza4lkOxQHTRkr_eVnEexHLhWks5uaJlJgaJpZM4WkqhV> .

[tisonkun]

Sounds good.

Could you clarify the steps bootstrap NQP on truffle backend? Seems we define TAST and port the underneath to truffle framework. Not really sure.

Not a emergent issue but I think it helps contributor understand how truffle backend works and the stage where it finally reaches.

[pmurias]

Nqp-truffle needs to get to the point when it can compile and run the whole NQP. Then we will compile NQP to truffle6 bytecode. We can run the bytecode with just the BytecodeRunner part and we won't need the JVM backend anymore.

…

On Wed, 12 Sep 2018 at 15:53, 陈梓立 ***@***.***> wrote: Sounds good. Could you clarify the steps bootstrap NQP on truffle backend? Seems we define TAST and port the underneath to truffle framework. Not really sure. Not a emergent issue but I think it helps contributor understand how truffle backend works and the stage where it finally reaches. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#500 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGXpnJe8IpwD8gE5fQM7e14hnSDhBPwks5uaRH0gaJpZM4WkqhV> .

[pmurias]

BTW. nqp-truffle is currently a bit in a state of chaos as I'm transitioning to loading the setting Hopefully things will get back to being a bit more sane in a few days (I'm hoping tomorrow).

…

On Sat, 22 Sep 2018 at 20:53, Paweł Murias ***@***.***> wrote: Nqp-truffle needs to get to the point when it can compile and run the whole NQP. Then we will compile NQP to truffle6 bytecode. We can run the bytecode with just the BytecodeRunner part and we won't need the JVM backend anymore. On Wed, 12 Sep 2018 at 15:53, 陈梓立 ***@***.***> wrote: > Sounds good. > > Could you clarify the steps bootstrap NQP on truffle backend? Seems we > define TAST and port the underneath to truffle framework. Not really > sure. > > Not a emergent issue but I think it helps contributor understand how > truffle backend works and the stage where it finally reaches. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#500 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAGXpnJe8IpwD8gE5fQM7e14hnSDhBPwks5uaRH0gaJpZM4WkqhV> > . >

[tisonkun]

Thanks for the explanation! Close this as the issue resolved.