3 ms·
None of the bugs in the first article are relevant today.
by amedvednikov 3y ago
None of the bugs in the first article are relevant today.
- pityJuke 3y agoAll I'll add is that whether or not that specific example holds up today matters little to the wider point: which is, that the language makes promises, and you need to verify each claim due to the repeated [0] ambiguity/inaccuracies about them. [0]: Across the span of the 2019-2022.
- delian66 3y agoIt is very easy to verify. Just have a working C compiler + git + make: git clone https://github.com/vlang/v cd v make ./v your_program.v On a modern machine with good network, it will take you under a minute, to have your own copy of latest V, and less than 200MB, including the .git/ folders. You can also download .zip releases from https://github.com/vlang/v/releases https://github.com/vlang/v/releases , without needing git. The .zips there are <15MB, and contain a prebuilt V executable, so you do not even need make to use it.