Xeorg
/
site
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update v-vvork-in-progress-2020-01-03.markdown

This commit is contained in:
Cadey Ratio 2020-01-03 16:59:09 -05:00 committed by GitHub
parent f1c5f047a5
commit ac6a9225aa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
blog/v-vvork-in-progress-2020-01-03.markdown
View File

@ -12,6 +12,8 @@ So, December has come and passed. I'm excited to see [V][vlang] 1.0 get released
as a stable production-ready release so I can write production applications in as a stable production-ready release so I can write production applications in
it! it!
NOTE: I was asked to write this post after version 1.0 was released in December.
[vlang]: https://vlang.io [vlang]: https://vlang.io
Looking at the [description of their github repo][v-github] over time, let's see Looking at the [description of their github repo][v-github] over time, let's see
@ -231,7 +233,17 @@ $ du -hs main
121M main 121M main
``` ```
Well that's a good chunk of it shaved off at least. Well that's a good chunk of it shaved off at least. It looks like there's no
dead code elimination at play. This probably explains why the binary is so big.
```console
$ strings main | grep hello | wc -l
1200000
```
Yep! It has all the strings. That's gonna be big no matter what you do. Maybe there
could be some clever snipping of things, but it's reasonable for that to not happen
by default.
## Hello World Leak ## Hello World Leak