V 0.3 is out! #14895
Replies: 12 comments 24 replies
-
|
What a time to be alive |
Beta Was this translation helpful? Give feedback.
-
|
I love the direction V has taken. Super happy I found this project early and I am forever impressed by its progress. |
Beta Was this translation helpful? Give feedback.
-
|
2 minute papers reference, awesome 😄 |
Beta Was this translation helpful? Give feedback.
-
Me too! |
Beta Was this translation helpful? Give feedback.
-
But wait, I thought they could for some time already. Edit: I think I got it - the list of updates is v0.3 compared to the initial release of the previous version, v0.24 |
Beta Was this translation helpful? Give feedback.
-
|
Compared to 0.2 :) |
Beta Was this translation helpful? Give feedback.
-
|
Damn!!! What an update! Absolutely brilliant!! Unrelated to this (and probably must have been asked many times): Thanks.. |
Beta Was this translation helpful? Give feedback.
-
|
Looking through the V website, everything with a scope it can just drop, and everything without a scope it manages through Garbage Control. So very similar to how a lot of languages (.NET, Java) do it. It does mean a slight overhead though. Rust adds that complexity so it can always know what the scope is. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @Deukhoofd :) |
Beta Was this translation helpful? Give feedback.
-
|
Most of Rust's complexity is brought by the elements through which memory management is done automatically and without a GC. That is ownership, borrowing, and lifetimes. Last year, while studying this V language I always wondered what's the main "competitive advantage" that brings in, while being in love with it. As long as you have a GC, you'll always be just another player in this area, without real major differentiating factors to attract people to use and contribute. According to what's even on homepage:
there's a chance to have no GC at all, with the expense (or risk) to take care of freeing the memory yourself. That's a pretty nice option, considering that you love the language and the whole developer experience. Am I right? 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
@dxps Hmm... I don't know much about how autofree is supposed to work, but, if it is what it sounds like, without the burden of complicated syntax, count me as fully sold on it... |
Beta Was this translation helpful? Give feedback.
-
|
Aggressively awaiting progress on volt, gitly, vinix, and many other tools written in V :D |
Beta Was this translation helpful? Give feedback.
-
|
Vinix can already run g++ and Doom, and we're launching Gitly next week! |
Beta Was this translation helpful? Give feedback.
-
|
It's unrealistically cool It's like the world is supposed to be like this - light and simple, but functional |
Beta Was this translation helpful? Give feedback.
-
|
@medvednikov I guess "next week" Gitly release has been post-poned? |
Beta Was this translation helpful? Give feedback.
-
|
@hakimio it's live |
Beta Was this translation helpful? Give feedback.
-
|
Awesome :) |
Beta Was this translation helpful? Give feedback.
-
|
Is the garbage collector here to stay? When can we expect some progress with |
Beta Was this translation helpful? Give feedback.
-
|
Yes, GC works great with V and is here to stay. It's actually faster than
Should be complete by 0.4 or 0.5. |
Beta Was this translation helpful? Give feedback.
-
|
GC by default, for convenience, and no memory leaks is quite acceptable. Definitely myself and others will want the option to be able to run without GC, but the convenience of not having to do manual either. To include for various reasons, and performance in certain situations can be among them, thus looking forward to autofree's continual development. The 3 options of GC, autofree, or manual will give V users very nice choices. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, the goal is to offer flexible memory management options, as explained on the home page. |
Beta Was this translation helpful? Give feedback.
-
|
autofree is unique in all the languages I know(dart,go,zig,odin,nim,nelua,carbon...), a very cool thing! So much so that I've been checking almost every day since the day I saw it to see if there's anything new about it. |
Beta Was this translation helpful? Give feedback.
-
|
@medvednikov I was wondering why autofree is not in ROADMAP.md? |
Beta Was this translation helpful? Give feedback.
-
|
Will the go backend use go’s runtime, make v’s go keyword behave just like go’s? |
Beta Was this translation helpful? Give feedback.
-
|
The Go backend compiles V to Go, and then generated Go code is compiled, so yes it will use Go's runtime. |
Beta Was this translation helpful? Give feedback.
-
|
Does the version 0.3 mean that the language specification is now almost finalized? |
Beta Was this translation helpful? Give feedback.
-
|
I guess. We don't have a formal spec yet, but would be nice to have. |
Beta Was this translation helpful? Give feedback.
-
|
the key reason for V's survival is performance. |
Beta Was this translation helpful? Give feedback.
-
|
V seems easier to learn & develop faster than Rust, which is the reason why some devs choose Go over Rust. |
Beta Was this translation helpful? Give feedback.
-
|
quite awesome, V is the most sane language created since C. Will be quite gratifying when we are done with our full transformation of our cloud platform ecosystem to be run and fully developed with V |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Glad you like it. |
Beta Was this translation helpful? Give feedback.
-
...... Then came V. And it hit the exact right spot. A single universal language for all domains. From embedded systems to large enterprise systems spanning multiple, heterogeneous clouds. If what is claimed about language is all true, be ready to face a lot of attacks on this language. Huge companies and huge many people are heavily invested into competing ecosystems..... My suggestion: Best wishes... |
Beta Was this translation helpful? Give feedback.
-
|
My dream programming language would be as fast as C, safe as Rust and as easy as Python. I think V and Vale are the promising languages in these aspects. The more I write Python code, the more I realize the importance of safety. |
Beta Was this translation helpful? Give feedback.
-
|
Great work. Thank you very much! I am curious if there are plans to improve on the threading system. I am looking for a more functional approach with lots of threads started by the But even with this I am not too sure that this would be sufficient to develop multi parallel code in a style one would do in Erlang etc. I know you already stated that you are going to improve here but what are your thoughts and maybe your timeline? |
Beta Was this translation helpful? Give feedback.
-
|
I only dip into this repo every now again to check on progress, so I've missed the news. Can someone catch me up on why Option and Result have ceased to be the same type? That was one of the features that I liked! |
Beta Was this translation helpful? Give feedback.
-
|
Too many complaints that people had to add extra code in the It is also very seldom that a routine would need to return both... if you need to return a |
Beta Was this translation helpful? Give feedback.
-
V 0.3 is out!
5769 commits pushed to master, 1697 bugs closed since V 0.2.
It's been a while since the last major release, from now on we'll do major releases every ≈4 months.
v translate file.c. (Demo video: Translating DOOM from C to V, building it in under a second and running it!)OptionandResultare now separate types:?Fooand!Foorespectively. Old code will continue working for 1 year and will result in a warning/hint.m[bad_key] or { ... },if x := arr[key] { ... }.ustringhas been replaced with[]rune(works just like in Go).v self). It eliminates unreachable branches and performs other simple optimizations and transformations.bytehas been renamed tou8. Old code will continue working for 1 year and will result in a warning/hint.datatypesmodule now hasHeap, Queue, Stack, BSTree, LinkedList.[]int{init: it}).>>>and>>>=have been added to V. (They work exactly like in Java.)-nofloatoption, which is useful for writing kernels and for embedded systems without an FPU (used in Vinix).unsafeonly (for example, for C interop).unsafe.compress.gzip.net/net.http/vwebfixes (also used for the upcoming Gitly launch).net.httpheaders are now enum fields instead of strings. This allows to avoid typos and offers autocomplete.rand).[heap].regexmodule.gg.draw_polygon_filled(), gg.draw_arc_empty()etc)gg.gg.for innow works with fixed arrays.vfmtcode when not invfmtmode (by using-d vfmt).#[index]syntax for negative indexing (like in Python, but needs special syntax instead of being used by default).pub).foo(bar()?)).const x := opt() or {}).syncimprovements includingsync.thread_id(),sync.Once..foo.o) that can be used in existing C projects.-usecacheand-skip-unusedfixes, they are close to being on by default.term.uiimprovements, including multi byte/UTF-8 events.cryptomodules, includingcrypto.des, crypto.cipher, crypto.blowfish.-d 4bytebool) for compatibility with some C software.strconv(pure V formatting module used in string interpolation) fixes and performance improvements.volatilekeyword."stringliteral".lenoptimization (replaced by the actual number by the newtransformpass).mathmodule.1_000_000.strings.Builderoptimizations and new methods.-autofreeflag).v -b go -o file.go file.v).isizeandusizetypes, deprecatesize_tin favor ofusize.datatypesanddatatypes.fsmmodules.compile_errorandcompile_warncomptime functions.with a much cleaner and faster implementation. Previously libc's
sprintfwas used.
unused variablewarning. Assigning to a variable no longer marks it as used.vwebnow uses struct embedding:app.vweb.text('hello') => app.text('hello').const()blocks:const x = 0.>,<,!=,==,<=and>=operators.User{ ...u, name: 'new' }to replace{ u | name: 'new' }.byte.str()has been fixed and works like all other numbers.byte.ascii_str()has been added.for mut x is string {}.[noinit]struct attribute to disallow direct struct initialization withFoo{}.[1, 2, 3]...is now...[1, 2, 3]enumasintand operations onenumexcept==and!=are removed for strict type checking.[manualfree] fn f1(){}and[manualfree] module m1, for functions doing their own memory management.<and>operators for struct in.sortmethod for arrays, i.e.arr.sort(a < b).+=,-=,*=,/=and%=if the operators are defined.gowith a generic function:go test<string>(c, 'abcd').x := $embed_file('v.png') println(x.len) println(ptr_str(x.data())), for embedding files into binaries.left()/rightwere removed in favor of slicing syntax:str[..pos].from local variables.
__offsetoffor low level needs (works likeoffsetofin C).$env('ENV_VAR').==and<operators and auto generate!=,>,<=and>=.dump(expr), i.e. tracing of both the location, name and value of an expressionfn sum(i ...int) int=>a := [2,3,4] println(sum(a...))Beta Was this translation helpful? Give feedback.
All reactions