zamberzand

7 ms·

1.
by zamberzand 3y ago
But I'm not pretending that autofree isn't documented as WIP, nor am I suggesting that anybody should use anything unintended. I am simply pointing out that a single claim from the article is still relevant to how V functions toda
2.
by zamberzand 3y ago
Sure (although I can't find anything like that on vlang.io myself), but your post was that "[n]one of the claims in this article are relevant now." It is still relevant that autofree does not work on heap-allocated structs. I
3.
by zamberzand 3y ago
Why isn't there a citation for this 90-100% number? I really am extremely curious where it comes from. As for why I am posting a similar message (not nearly the same post, though) to you here as I did a year ago: It is because I am ver
4.
by zamberzand 3y ago
The homepage still makes the claim that "[autofree] takes care of most objects (~90-100%): the compiler inserts necessary free calls automatically during compilation." There is no citation for where this 90-100% number comes from,
5.
by zamberzand 3y ago
This is not quite true. The claims about autofree made in the article are still extremely relevant. For example, the following code from the article still leaks with autofree: [heap] struct MyHeapValue { value i64 } fn dr
6.
by zamberzand 4y ago
Trans woman here, here are my thoughts: So, research into the impact of biological sex on medication, and similar, doesn't really seem alienating to me. Despite the existence of trans people, there are obviously two main categories tha
7.
by zamberzand 4y ago
It seems we are essentially in agreement on how the documentation is meant to be read, which is that the points it makes about autofree are not meant to be statements of fact.
8.
by zamberzand 4y ago
I understand that autofree is WIP. I read that part of the docs, and I have watched the demo. But I don't really understand what the intended reading of the documentation is. If I were to completely take these two paragraphs out of con
9.
by zamberzand 4y ago
Okay, I really don't understand what you're saying here. The claims are objectively false. The autofree engine objectively does not free 90%-100% of objects, it is objectively not true that "It just works." If I unders
10.
by zamberzand 4y ago
So, to be clear, is the intended reading of the documentation as follows? > Most objects (~90-100%) are freed by V's autofree engine: the compiler inserts necessary free calls automatically during compilation. Remaining small percen
11.
by zamberzand 4y ago
In my opinion, the current documentation on the autofree engine [0] constitutes a false claim about language capabilities: > Most objects (~90-100%) are freed by V's autofree engine: the compiler inserts necessary free calls automat