e5484cec0e
Use custom wrap-around type instead of RangeInclusive Two reasons: 1. More memory is allocated than necessary for `valid_range` in `Scalar`. The range is not used as an iterator and `exhausted` is never used. 2. `contains`, `count` etc. methods in `RangeInclusive` are doing very unhelpful(and dangerous!) things when used as a wrap-around range. - In general this PR wants to limit potentially confusing methods, that have a low probability of working. Doing a local perf run, every metric shows improvement except for instructions. Max-rss seem to have a very consistent improvement. Sorry - newbie here, probably doing something wrong. |
||
|---|---|---|
| .. | ||
| borrow_check | ||
| const_eval | ||
| dataflow | ||
| interpret | ||
| monomorphize | ||
| transform | ||
| util | ||
| lib.rs | ||
| shim.rs | ||