vlang1dot0

11 ms·

61.
by vlang1dot0 6y ago
You're right but at the same time people also need to evaluate the state of the language with respect to the claims made on the home page. - autofree not only leaks memory but in some cases causes double frees or use after free resulti
62.
by vlang1dot0 6y ago
Bootstrapping the compiler isn't a sign of language maturity. V has changed pretty significantly both in terms of syntax as well as semantics since that release. Regarding compile times, why do you claim less than one second when your
63.
by vlang1dot0 6y ago
I think having actual documentation about how the memory system is supposed to work would do a lot more to answer questions than linking to the tests. For example: x = [1, 2, 3] // is this stack or heap allocated? foo(&x) &#x2
64.
by vlang1dot0 6y ago
All memory leaks in C are one line of code away as well (calling free() in some place).
65.
by vlang1dot0 6y ago
Ok but then the author should not be claiming that. The problem with V is that the author makes astounding claims and when people push back on that even slightly they get harassed. Even your comment nit-picks mine over technicalities while
66.
by vlang1dot0 6y ago
Even garbage collected languages do not prevent leaking memory because doing so requires understanding programmer intent. For example, adding objects to a static hash map and never using them is a memory leak that no GC will fix. V has the
67.
by vlang1dot0 6y ago
Ah yes, you're totally right. I didn't realize there was quite a bit of additional content "below the fold" on that page.
68.
by vlang1dot0 6y ago
Reading the Media Guidelines, I don't see how you came to that conclusion: > TL;DR: Most non-commercial uses of the Rust/Cargo names and logos are allowed and do not require permission; most commercial uses require permission.
69.
by vlang1dot0 6y ago
I don't really agree. The vast majority of applications are fine being written in whatever flavor of high-level, garbage collected, memory safe language you want. There are many nice options with pretty much any set of feature and styl
70.
by vlang1dot0 6y ago
dotnet and Rust are essentially neck and neck on plain text. On any benchmark that actually does work though, dotnet is nowhere to be found (less than half the performance of actix).
71.
by vlang1dot0 6y ago
Apologies but as your comment currently stands, it reads to me like "in theory yes, but actually no".
72.
by vlang1dot0 6y ago
LLVM has nothing to do with `const` evaluation in Rust. `const` evaluation happens at the MIR level which participates in incremental compilation.
73.
by vlang1dot0 6y ago
Who outside of Microsoft is going to have experience with the Windows build system? Is this like recruiters looking for 20 years of Go experience lol?
74.
by vlang1dot0 6y ago
> These kinds of “wacky types” are things you can statically analyze but not really “compile” per se. That’s why it’s a good fit for being transpiled down to a language with no types at all. > TL;DR, TypeScript is not really a “typed
75.
by vlang1dot0 6y ago
>> Nexus was a reasonably priced unlocked reference phone targeted to Power Users Nexus One: $530 Nexus S: $530 Galaxy Nexus: $200 with standard 2 year contract (basically the same as any flagship phone at that time) Nexus 4: $300 Nex
76.
by vlang1dot0 6y ago
My point still stands: is this UB or not? foo := charptr(0) x := *foo The "wasm" playground generates no compiler errors or warnings. In fact, the compiler seems happy to accept any number of dereferences as this
77.
by vlang1dot0 6y ago
Yes, please continue unraveling this "Scooby Doo mystery", I'm sure it will be entertaining for everyone! Do you think there's a coordinated campaign by(?) Coverity to get your open source project to use it? For what rea
78.
by vlang1dot0 6y ago
The problem is that V claims: - As fast as C - No manual memory management - No GC - Memory safety - Not hard like Rust You have fundamentally conflicting requirements. Saying "we'll do it like lobster" does not solve that. L
79.
by vlang1dot0 6y ago
> regarding lobster memory management: > the scope of anonymous functions cannot outlive variables' scope they reference, however V plans full closure support > lobster compiles whole codebase at once (so it can properly
80.
by vlang1dot0 6y ago
There are certainly some good reasons to use C as your backend, but there are some huge downsides as well. The main one in my mind is that you're limited by restrictions placed on you by the target language. V claims no UB but C has lo
81.
by vlang1dot0 6y ago
> 1. Option/Result are unified into a single type, ?T. This is not a positive. Option<T> and Result<T, E> have semantically different meanings. This is like saying integers and strings have been unified into a single typ
82.
by vlang1dot0 6y ago
It's not about the author being a CS major or how the parser is implemented. It's about the author being completely wrong and unwilling to admit it ("parsers are why compilers are slow" -> v 0.2 gets a parser) and bei