diff options
| author | Christine Dodrill <me@christine.website> | 2020-01-03 17:01:50 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-03 17:01:50 -0500 |
| commit | d93d0f361b1c4cbfe6de449eee02c05b2cd660a6 (patch) | |
| tree | 8186f42f55686b5634687e68e11a6b32966f6aaa | |
| parent | ac6a9225aa6652b641b5c2bd871e4050c32cff83 (diff) | |
| download | xesite-d93d0f361b1c4cbfe6de449eee02c05b2cd660a6.tar.xz xesite-d93d0f361b1c4cbfe6de449eee02c05b2cd660a6.zip | |
Update v-vvork-in-progress-2020-01-03.markdown
| -rw-r--r-- | blog/v-vvork-in-progress-2020-01-03.markdown | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/blog/v-vvork-in-progress-2020-01-03.markdown b/blog/v-vvork-in-progress-2020-01-03.markdown index 731dea5..a0d0def 100644 --- a/blog/v-vvork-in-progress-2020-01-03.markdown +++ b/blog/v-vvork-in-progress-2020-01-03.markdown @@ -309,6 +309,10 @@ means that the compiler has overall gained 0.8 megabytes of leak in the last 6 months. This is worrying, given that V claims to not have a garbage collector. I can only wonder how much ram was leaked when building that giant module. +> If your V program compiles, it's guaranteed that it's going to be leak free. + +Quoted [from here](https://web.archive.org/web/20200103220131/https://vlang.io/docs). + For giggles, let's see if V in module mode leaks ram somehow: ```console |