- Notifications
You must be signed in to change notification settings - Fork 220
Open
2 / 142 of 14 issues completedLabels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failurestype-enhancementA request for a change that isn't a bugA request for a change that isn't a bugtype-performance
Description
I've been digging into build_runner performance, and in particular, scalability of analyzer-based generators as the codebase grows.
It looks like there is room for significant improvement, so that's good :)
It's complicated, so I will need to move carefully with details discussed as I go.
First job will be to add some benchmarks #1335.
pedromassango, mark-dropbear, jodinathan, orestesgaolin, Reprevise and 125 moremrgnhnt96, Ehesp, albertms10, HE-LU, Gabriehl and 18 morealbertms10, HE-LU, Gabriehl, pedromassango, tenhobi and 12 morenotDmDrl, SlayerOrnstein, albertms10, HE-LU, Gabriehl and 11 more
Sub-issues
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failurestype-enhancementA request for a change that isn't a bugA request for a change that isn't a bugtype-performance