| Code-Review | +1 |
final id = unit == 'M' ? 0 : int.parse(unit.substring(1));Can we use `'${moduleNameToId(unit) + 1}'` here?
final moduleId = moduleIdString == 'M'Ditto use `moduleNameToId`
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
final id = unit == 'M' ? 0 : int.parse(unit.substring(1));Can we use `'${moduleNameToId(unit) + 1}'` here?
Done
final moduleId = moduleIdString == 'M'Martin KustermannDitto use `moduleNameToId`
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
PTAL, it lost the +1 bit after addressing comments & rebasing
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[dart2wasm] Use M / M<id> for module names
The module names can appear in stack traces (**). In order to make
stack trace parsing safe and allow recognizing the module name in
stack trace frames we are limited by the characters we can use.
At the bare minimum we should use url-safe characters instead of
what we do now. But the names aren't so important, because
a) it's one char in a wasm module
b) deferred modules only import main module (never other
deferred modules)
So whether we can save an extra 1-3 bytes in the name isn't so
important. We only really care about the main module's
import name, as deferred modules use that.
This CL switches us to use
* `M` (main module)
* `M<id>` (deferred modules)
naming convention
We no longer distinguish `--minify` from `--no-minify`.
=> Easy to see module id by looking at a name
=> Easy to parse
(**) Wasm runtimes that don't know where the wasm module bytes
come from (i.e. no known uri / file name) will fallback to
show module names in stack traces.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |