V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

tuananh wrote: post #3

it's very impressive to know this is one person's work. i first heard of him via Volt app. and then he went on to create vlang which looks very good from what i've seen

Thanks!

I no longer work alone though, we have a large team, and I think only about 50% of code is written by me at this point.

Although the autofree engine this video is about is fully my work.

Re: V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

#5

Post by jokethrowaway » Sun, Dec 20, 2020, 2:11 PM UTC

So this is basically a go-like language which can be compiled into C (which would explain fast compilation small size)? Neat!

I guess community and adoption will make it or break it

Re: V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

#6

Post by amedvednikov » Sun, Dec 20, 2020, 2:12 PM UTC

jokethrowaway wrote: post #5

So this is basically a go-like language which can be compiled into C (which would explain fast compilation small size)? Neat! I guess community and adoption will make it or break it

Yes, but it improves quite a lot on Go:

https://vlang.io/compare#go

Re: V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

#7

Post by vsskanth » Sun, Dec 20, 2020, 2:57 PM UTC

Very happy to see vlang make steady progress. Been following this language since it was initially posted on HN.

What is the trade off here with auto free ? Is it still possible to have memory leaks in some scenarios ?

What about concurrency or multi threaded situations ?

Re: V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

#8

Post by amedvednikov » Sun, Dec 20, 2020, 3:04 PM UTC

vsskanth wrote: post #7

Very happy to see vlang make steady progress. Been following this language since it was initially posted on HN. What is the trade off here with auto free ? Is it still possible to have memory leaks in some scenarios ? What about concurrency or multi threaded situations ?

Right now it's possible to have leaks due to bugs in the autofree engine. Once it's stable, there will be no leaks.

For mutable objects shared across threads, reference counting will be used.

Re: V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

#9

Post by pipologist » Sun, Dec 20, 2020, 4:22 PM UTC

Nice work. V is coming along nicely. How would you say the autofree engine works, is it RAII?

Re: V compile time memory management:Running the Ved-editor on 8MB file with 0 leaks

#10

Post by amedvednikov » Sun, Dec 20, 2020, 4:31 PM UTC

pipologist wrote: post #9

Nice work. V is coming along nicely. How would you say the autofree engine works, is it RAII?

Yes, pretty much.