Potential optimization: Auto AOT when possible, and fallback to interpreted about dart_eval HOT 7 OPEN

The first part of doing this is covered in #53 and ethanblake4/flutter_eval#3 which I would like to have working in v0.6 (next major release).

The second part is basically some kind of auto-diffing to see what has changed since the last version. I have thought about that but it's definitely a 1.0 or post-1.0 feature.

from dart_eval.

The first part of doing this is covered in #53 and ethanblake4/flutter_eval#3 which I would like to have working in v0.6 (next major release).

Looking forward to that!

some kind of auto-diffing to see what has changed since the last version.

For a minimalist solution (which does create false positive though) - Maybe just generate bytecode for each and every code, and check equality?

from dart_eval.

For a minimalist solution (which does create false positive though) - Maybe just generate bytecode for each and every code, and check equality?

I don't really understand, can you explain more? What is it checking equality to?

from dart_eval.

Checking eq of bytecode bytes?

from dart_eval.

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 works (even a minor change to one part of the code can cause a lot of bytecodes to change, because they can store absolute offsets for functions/jumps which get 'pushed' by all previous changes)

from dart_eval.

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

from dart_eval.

Oh I see. That is a problem

from dart_eval.