Ethan

So you are saying, generate bytecode for 'before' and 'after' case and then just see what has changed? Unfortunately i don't think that's possible due to the way the bytecode...

I will add though, it maybe should not work like that because it's also annoying for incremental compilation. Maybe we can do that then if I end up changing it

Boxing is _very_ core to how dart_eval functions (and is inspired by the way Dart itself functions). The only reasonable option besides boxing is to tag every object created natively...

Good idea, but right now dart_eval does not support enough features (eg. try/catch) to do this I think. I will look at this again maybe around v1.0 release when most...

@lancexin That's a really cool project. However due to dart_eval's bridging functionality, it would be hard to use the front_end package. Because for example in dart_eval you can extend a...

Good idea. Do you know where these tests are? If not I'll poke around and see what I can find when I have time

Some good ones here: https://github.com/dart-lang/sdk/tree/main/tests/language Would be a good project for a contributor IMO, I'll add help wanted / good first issue. For anyone who does want to take this...

Basic support added in v0.6.0

Hi, I can't reproduce this issue in dart_eval v0.6.5. I created the following test: ```dart test('Future method with args', () async { final runtime = compiler.compileWriteAndLoad({ 'example': { 'main.dart': '''...

> the ultimate solution to Flutter hot update I would love for it to be this and I am committed to continuing to improving it. That said, I don't currently...