diff options
| author | Christine Dodrill <me@christine.website> | 2020-06-17 10:39:47 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-17 10:39:47 -0400 |
| commit | 956b930965513af3f611c55e5cf5aba31311df6c (patch) | |
| tree | ac62464cabf02e558ed7fcf9a0f150e3df2f4db0 | |
| parent | eaf6c9469d040f8db8d002dc3a37896b4c78b873 (diff) | |
| download | xesite-956b930965513af3f611c55e5cf5aba31311df6c.tar.xz xesite-956b930965513af3f611c55e5cf5aba31311df6c.zip | |
Update vlang-update-2020-06-17.markdown
| -rw-r--r-- | blog/vlang-update-2020-06-17.markdown | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/blog/vlang-update-2020-06-17.markdown b/blog/vlang-update-2020-06-17.markdown index 0811cd7..f0fb253 100644 --- a/blog/vlang-update-2020-06-17.markdown +++ b/blog/vlang-update-2020-06-17.markdown @@ -102,7 +102,7 @@ $ valgrind ./v hello.v ``` It seems that the memory managment really is a work in progress. This increase in -leakage means that the compiler building itself now creates `30,409,141` bytes of +leakage means that the compiler building itself now creates `7,232,779` bytes of leaked ram (which if i recall is actually a remarkable improvement). However, `hello world` seems to leak again: |