News for hackers. Stuff that matters.
Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:01AM (#31947321)
A 0.3 language feature that is marked as "not ready for production" on the website have bugs. How unexpected.
Re:V 0.3 by wb13579 on Friday July 01, 2022 @11:09AM (#31947455)
That's what I thought.

Last time it seemed impossible, you said it was "work in progress" for years, and it turned out to be a lie.

This time it seems impossible, and it's been "work in progress" for 1.5 years. You can see why that's suspicious.

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:20AM (#31947622)
You have a very strange definition of a lie. There's a working example. Anyone can run it and inspect it, it's all open source.

Autofree hasn't been a priority because of how unexpectedly well the GC is performing with V, but it will be finished.

All this is clearly stated on the website.

Re:V 0.3 by wb13579 on Friday July 01, 2022 @11:32AM (#31947835)
Your claim of "(Work in progress) There's no garbage collection or reference counting. V cleans everything up during compilation. If your V program compiles, it's guaranteed that it's going to be leak free." was absolutely a lie. That's why you had to eventually fall back to reference counting.

The newer reference counting system has an example but it's very easy to conjure a working example of a system that has fundamental holes. When people use it for larger programs it crashes or leaks even today. Is that incorrect?