@codetothemoon

ERRATA: At around 7:00, I explain what the vision for autofree is. I say that it aims to automatically distinguish between cases where something needs to be deallocated at the end of the scope it was defined in, and cases where runtime reference counting is needed. But I skirted over one of its core value props - and that is that it aims to determine at compile time when memory is no longer needed and deallocate that memory, even when that place is not in the same scope where the memory was allocated. The claim is that it can do this without a runtime reference count in the vast majority of scenarios, but will fall back to runtime reference counting in the cases where it can't.

@n_kwadwo

As a Go programmer I think I already know V

@dkwdvnte

Interesting video, although it reminds me a lot of Go, thank you anyways! Could you review Crystal lang next?

@al1gned

As a go programmer I already feel entitled to try it, thanks for such a detailed video.
Also, what colorscheme are you using in your editor? Monokai? Looks so calm and classy.

@phenanrithe

Very interesting! I'm also wondering how the autofree works. I'm a little concerned that it conceals potential leaks by circular references without the user knowing from just looking at the code. Or just very late freeing of objects.

@jimmyneutron129

the idea seems cool, will wait to see how it evolves. a bit strange to incorporate gui right into when it is on version 0.4

@pumpkinjutsu1249

What is the font used? The parentheses are gorgeous!

@mwnkt

really loving the videos, btw what editor do you use

@sinom

C++ smart pointers (unique_ptr and shared_prt) exist and have existed in the standard for over a decade now (2011) and have existed in the boost library for almost 2 decades (2004). They handle the freeing for when the variable goes out of scope. 
Yes you can also use manual new/delete and manual malloc/free but you only rarely actually have to do that and usually shouldn't do that.

@sp.n7401

Nim also has ARC memory management that's becoming default in 2.0 (current devel).

@DeepSeekAgent301

OMG, language so advanced, i love it ,  how is this possible?

@godofbiscuitssf

Apple platforms with Objective C and Swift have had ARC (automatic reference counting) for a decade.  before that, Objective C had manual reference counting with semi-automatic reference counting using autorelease pools.    

the LLVM front-end, Clang, inserts allocs and deallocs into the code on your behalf with each trip through the compiler, not as part of your source code. No performance hit above what manual memory management would cost you otherwise, and autorelease pools would in many circumstances improve performance by allowing you to use/reuse local memory pools (say, within tighter loops) that you could free up upon exiting scope or keep around but clear out if you know you're going to reuse it.  

But like I said, a decade or more.

@MegaMage79

Cool video. What font are you using ?

@sinom

3:40 that looks a lot like captures in c++ lambdas. Looking at the doc's they are similar just that they don't support wildcards and are always capture by copy.
The docs for function captures also showcase that references in V are in themselves also basically just pointers that if you copy you get another reference instead of a copy of the underlying object which I don't really like.

@delian66

Thanks for trying V, and for the unbiased review about it.

@shapedthought

Funny you posted this video I bought the book last weekend, very promising but there are some bits I'm still not sold on.

@theherk

Been following it for a few years now, and it doesn't ever seems to be moving along as quickly as its claims do. Pretty uninteresting when the field is filled with so many great languages currently.

@007kowalski

Now that you mention Nim, I really feel it deserves a lot more attention, hopefully you can dive into it with some practical examples.

@MrAbrazildo

1:48, ouch! I don't want to specify the returning type! 3:03, ouch! I want this to be automatic!
6:31, std::unique_ptr frees that memory automatically. 6:42, C++'s std::shared_prt is meant for this RC.
6:55, are you saying 'deallocate' meaning 'free from stack' too? Because in C++ things are build on stack by default. For instance: auto a = Thing. It's recommended freeing the stack as soon as possible, because it's precious memory, as small as faster.

@Viralvlogvideos

Great video learned a lot, bro can you please tell me what extension your using to add that sound effect when your typing the code. It sounds too good