Liam Appelbe
Liam Appelbe
This was fixed by the isolate lifecycle refactor
Since we don't have `package:test` support for workspaces, the way to run all the workspace tests in a single command at the moment is to manually specify all the test...
In theory they're only generated as needed, but there's probably a bug somewhere where I'm deleting a method for one reason or another and not cleaning this up. Bugs like...
I'm not sure a `closeToken` would solve the problem. You'd still be trying to delete the callback during the isolate shutdown flow, which is risky. Depending on the exact order...
> I've thought about this as well, and I wonder a bit if that doesn't defeat the point of making callables closable from native code. This is what I was...
Related: https://github.com/dart-lang/native/issues/1510
Does every block/protocol method need to have a context object, even if they're not going to use it? This would add a small memory and performance overhead, as well as...
The issue is much more specific than I originally thought. I'm not able to reproduce it in a toy example. The [code_assets examples](https://github.com/dart-lang/native/blob/main/pkgs/code_assets/example) I tried work fine under `test_with_coverage`, including...
New hypothesis: if a library you're importing uses native assets, those will fail to load when running via `test_with_coverage`. I'll test this tomorrow.
Nope, it's not just a matter of depending on a package with native assets. Toy examples using that pattern also don't repro the bug.