diff options
| -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 |