3 ms·
A demo, sure. But answer us this: does autofree ever crash, and does autofree ever leak?
by wb13579 4y ago
A demo, sure. But answer us this: does autofree ever crash, and does autofree ever leak?
- amedvednikov 4y agoA 0.3 language feature that is marked as "not ready for production" on the website have bugs. How unexpected.
- wb13579 4y agoThat'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.
- amedvednikov 4y agoYou 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.
- wb13579 4y agoYour 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?