News for hackers. Stuff that matters.
Re:V 0.3 by ketzu on Friday July 01, 2022 @11:49AM (#31948144)
I disaggree [1] with your claim that all issues have been fixed, but maybe I misunderstand what "No nulls" means and other things.

> What's wrong with the division by zero issue?

It is undefined behavior in C. [2] section 6.5.5 the 5th paragraph. V generates code that is undefined behavior in the intermediate language, some people might consider that "undefined behavior".

> It works just like in Go?

I read this argument in the issue too. How is that remotely relevant?

> What about the openssl issue?

I linked issues of things that were mentioned in the initial review. Not issues that were problematic, remarkable or anything else.

[1] https://news.ycombinator.com/item?id=31947510

[2] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf

Re:V 0.3 by amedvednikov on Friday July 01, 2022 @11:53AM (#31948211)
> I read this argument in the issue too. How is that remotely relevant?

How is that remotely irrelevant?

What kind of behavior do you expect?

Re:V 0.3 by sjustinas on Friday July 01, 2022 @02:49PM (#31950975)
Not the parent poster, but there seems to be some misunderstanding. The GitHub issue creator explained that they're getting two different behaviors depending on C compile flags. That's already not "the same behavior as Go" AFAIK.

> What kind of behavior do you expect?

Defined behavior, I assume. If V uses C as an intermediate, and the generated C code invokes undefined behavior, then V can not guarantee "no UB" in that case at all. It is completely up to the C compiler what happens. Even if the compiled app behaves "properly, like Go" with the specific C compiler, with the specific flags, on that specific machine, does not mean this behavior is defined and consistent.