diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2021-04-21 19:30:28 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2021-04-21 19:30:28 -0700 |
commit | 25791d90326a19080136f768c0a303f4ab7da890 (patch) | |
tree | be0ee6754e1968999b6e80a5abaf896d011e2615 /shell | |
parent | a8fb537a88fdbe77cdcbaa05ee28d1cad94550da (diff) | |
download | mu-25791d90326a19080136f768c0a303f4ab7da890.tar.gz |
opt: don't clear streams of bytes on the stack
All over the Mu code I reflexively initialize all variables just to keep unsafe SubX easy to debug. However I don't really need to do this for safe Mu code, since the type- and memory-safety already ensures we can't read from streams beyond what we've written to them. For now I'll continue mostly with the same approach, but with one exception for streams of bytes. Mu programs often emit traces, and in doing so they often use temporary streams of bytes that can get quite long. I'm hoping avoiding initializing KBs of data all over the place will measurably speed up the Mu shell.
Diffstat (limited to 'shell')
0 files changed, 0 insertions, 0 deletions