182812a278
@kha This one was crazy, the compiler created a join point for the continuation of the match-expression. Each case of the match was invoking the join point with a different parser. Two of the branches were the partially applied `reader_t.bind` and `reader_t.orelse`. This change did not improve the performance much, but it makes sure we don't waste time trying to figure out why we have these two partial applications in the call graph. |
||
|---|---|---|
| .. | ||
| control | ||
| data | ||
| lean | ||
| coe.lean | ||
| core.lean | ||
| default.lean | ||
| env_ext.lean | ||
| function.lean | ||
| init.md | ||
| io.lean | ||
| platform.lean | ||
| util.lean | ||
| version.lean.in | ||
| wf.lean | ||