7 ms·
https://news.ycombinator.com/item?id=31063731 https://news.ycombinator.com/item?id=31063731
by bheadmaster 5y ago
https://news.ycombinator.com/item?id=31063731 https://news.ycombinator.com/item?id=31063731
- amedvednikov 5y agoThere are no trivial examples unable to output correct code in that comment. Your attempts to discredit the language are just sad.
- paskozdilar 5y agoAlright, you cheeky bastard. It's on. You can expect a deep (and public) analysis of everything you've done with V in a couple of months. We'll see who's right.
- dundarious 5y agoAll of those issues are related to autofree. From vlang.io: > Note: right now autofree is hidden behind the -autofree flag. It will be enabled by default in V 0.3. I'm assuming because it's not considered good enough quality yet. It would be better to be explicit about that, but it's not unreasonable as-is. I think it's only reasonable to mostly ignore autofree issues when assessing whether the language has trivial issues. Count all those issues as a single "autofree is alpha quality" conceptual issue. Counting each individual autofree issue in order to convey the sense that there is a critical mass of issues in the project in general is quite harsh, I think.