It's not probably anymore, you're too late. See the message below.
And no, 800 bytes is not a serious matter.
And no, 800 bytes is not a serious matter.
A leak is a valid concern, because it implies problems with memory management.
"We choose to not free some memory on purpose" can be a valid explanation , but needs more context.
You could be more persuasive by linking to the relevant code and explaining what memory it is and why you are leaking it.
Otherwise your responses just seem like deflection.
This is completely irrelevant. Each V program uses an extra 800 bytes.
If you look at what actual performance and low resource usage V brings to the table, you'll see it's not a problem at all.
My post wasn't about this concrete issue, which can also be explained.
My point is about a civil discourse culture driven by (precise) technical arguments,not hostility or deflection. Which I am not seeing, which is why you only increase the skepticism here rather than change minds.
Unless the leak was actually unintended and is a bug.
But that's also fine, any language (old or new) has heaps of bugs in all corners of the codebase. But then just own up, explain and fix it.
> Wanna know something funnier also posted in previous thread?
This wasn't a good faith attempt to report a bug from the beginning. It's just an attempt to score points off of V.
> I find it funny that as soon as you asked someone to list these major bugs [...] they begin to continue their regular deflection and dodging of the question.
which I found dishonest (especially since those bugs are well described in the post the commenter linked) as the exact opposite happened in the same thread.
If I may, I still believe even 1 byte is a serious matter imho.
This doesn't happen, we have V web services running for months without leaks.
But since there were several responses with this message, I'll make sure valgrind reports 0 :)
I also don't appreciate whataboutism, sorry.