Hacker News new | ask | show | jobs
by theamk 1463 days ago
What do you mean "falsely accusing"? Looks like Xe's blog was correct, V was vaporware back than.

According to this post, it still kinda is.. At least the most interesting parts like unique memory management is 100% vaporware.

1 comments

It wasn't vaporware back then, it isn't now.

Here's a 1.5 year old demo of V's autofree working:

https://www.youtube.com/watch?v=gmB8ea8uLsM

Again!! Same video you've been throwing on whoever asks about "autofree", knowing very well that it doesn't work.

I asked this question before and was banned on discord, do you have control flow graph analysis anywhere in V? If not, how do you suppose your autofree engine would work flawlessly?

Also, we now have an operating system Vinix, which uses autofree. Does that work as a proof for you or is that also not enough?
And that's why vinix [1] is full of manual free calls? That tells how good autofree is, isn't it? Can you compile v compiler with autofree? Last time I checked, you can't.

[1] https://github.com/vlang/vinix/search?q=free&type=code

Because surprise it's 0.2, and autofree has bugs, can you imagine?
Nowhere from homepage you get the clue that it's 0.2, do you?
You can actually compile the V compiler with -autofree.

The resulting executable however does segfault - try it with:

    ./v -autofree -o x cmd/v
    ./x version
You seem to talk a lot about things, that you are not well informed about.
> The resulting executable however does segfault

Doesn't give lot of confidence that it works, does it?

> You seem to talk a lot about things, that you are not well informed about.

Unlucky for you, it's not discord, you can't ban me here. So freaking deal with it.

Nobody bans for questions.

And the video I posted proves that it works. Keeping saying "it doesn't work" is ridiculous.

Your demo includes code that uses manual memory management because of autofree bugs.

https://github.com/vlang/ved/blob/9b85e6291c9fe9135db1e300de...