delian66

What you describe is exactly what the V compiler does.

It produces warnings for unused variables, and warnings become errors, when you want to compile a production executable with -prod , so you can get both the benefit of prototyping without losing your flow, and you are still required to cleanup after that, when you are finished, before release.

The absolute size of taxes over time?

"Hanging on in quiet desperation is the English way."

@ModernMech, you can just address people here individually, and not refer to them as V developers or V community - that currently is already too broad and paints people that you do not know at all, with the same paint, be it bright or dark.

It is the same, as asking you to not talk about all Australians, all Chinese or all Bulgarians, when you mean the actions of specific people/individuals.

That is all I am asking for, and I think that is not difficult to understand.

Have a good day too (I can not respond further to your comment below).

If you mean the table under "For comparison, space and time required to build each compiler", I think, that it is about what each compiler took in time and disk space to compile itself, on the same hardware, so it is about P compiling P sources.

V can not compile C or Go, Go can not compile C, and C compilers can not compile V or Go, so it can not be otherwise.

> I never claimed to be anything, and I have no dead or flagged comments.

You just said yourself, that you are an asshole, rude and blunt, after insulting a whole community of people ... Have you thought, that maybe you should stop?

> Or you can roll around with pigs like me and get a reputation for being muddy.

I am a farmer. I live in a village in Bulgaria, and I've had to deal with actual pigs before from time to time... Pigs should know their place, and it is not, where people discuss ideas.

I think you are delusional. I do not send any people anywhere.

All people on HN are individuals, not some kind of a collective Borg.

My job, thank God, is not to please entitled rude people on HN.

If you have some problem, you can simply address people individually, without attacking an entire community of many, that share a common interest in a programming language.

Thank you for the constructive criticism, for which HN, was once famous for, and which hopefully will return.

I would appreciate, for you to not speak about the V community and V devs, which consists of many people (660 contributors currently), with various positions and attitudes, including me.

I have not spoken about anyone being a salty rival, whatever that means.

Thanks in advance.

Sorry, I do not understand.

Each line of what?

It is very easy to verify. Just have a working C compiler + git + make:

    git clone https://github.com/vlang/v
    cd v
    make
    ./v your_program.v

On a modern machine with good network, it will take you under a minute, to have your own copy of latest V, and less than 200MB, including the .git/ folders.

You can also download .zip releases from https://github.com/vlang/v/releases , without needing git. The .zips there are <15MB, and contain a prebuilt V executable, so you do not even need make to use it.

The main claim, about V doing something in 1s, is about V compiling itself from source, on a modestly modern machine.

That is mainly because of how it is organized. tcc also compiles itself fast, because of how it works, and how it is organised.

That other compilers, like rustc, gcc or clang can not do it, because they have other priorities/tradeoffs, is their problem.

By default it does use tcc on most platforms, because tcc is awesome for quickly compiling C, and so iteration while prototyping with it is usually much more enjoyable than with gcc, clang or msvc.

You can pass `-cc gcc` to use another C compiler for example, instead of tcc.

There is also a native backend, that generates executables directly, without generating C, then using a C compiler to compile it. You can use `-b native` to try it, instead of the more developed C backend. Note that the native backend, is still work in progress though and it does not support some language constructs.

Why 250+ years?

In a way, I think this story is the opposite, of what would have happened, if an artist made a photograph picture, and presented it, as a hyper realistic painting, back in the days where photography was in its infancy.

I like to think they were.

What have you created personally, that give you the right to want to destroy the creations of others?

Can you link to specific examples please?

Why did it prove to be a red herring?

I could write a CLI or GUI Java program, that would run on any OS, for which there is a JVM, and that was easier than doing it in C, C++, Delphi or Perl, which were popular at the time.

As far as I know, at the time only TCL/TK offered something remotely comparable in portability for GUI apps.

Why is that?

Yes you have hit your limit in this particular area, but do not worry about it.

There is a saying that “A change of perspective is worth 80 IQ points.”, frequently attributed to Alan Kay.

In this particular case, you just need to look at 2D complex numbers, and what their multiplication looks like on a plane, and you will then have an intuitive understanding about i, as others have already pointed out.

From https://www.merriam-webster.com/dictionary/privileged :

    1 : having or enjoying one or more privileges, privileged classes
    2 : not subject to the usual rules or penalties because of some special circumstance 

"having good circumstances" does not have the same meaning. For example you can have good circumstances by luck, or by good timing, without having any privileges.

I have never banned people on any platform.

Letting them speak and reveal how vile they are is better in my experience.

It is a statement of fact. Everyone is free to make their own conclusions from that fact.

You can actually compile the V compiler with -autofree.

The resulting executable however does segfault - try it with:

    ./v -autofree -o x cmd/v
    ./x version

You seem to talk a lot about things, that you are not well informed about.

Yes, it is a null pointer, produced by the initialization to 0, as you noticed.

That is the current state - V wants to prevent setting pointers to arbitrary values, including 0, outside of unsafe code, but not all cases are checked yet, and you can get one. For example, you can also still cast numbers to pointers without unsafe{}:

    x := voidptr(0)
    println(x)

... and that will compile without an error, and produce `0x0`.

You can also search the issues, and find other examples of code, that ultimately produced null pointers.

Yes, there is a good possible outcome - they post it, we see it, and then, if possible, we take corrective actions.

Especially after writing "people will assume that being an asshole is a representative sample of those groups. It is not, but logic is not this species' strong suit."

=> xena does acknowledge, that most people will assume that the whole V community is hateful, and even then, used terms like "V cult" and "hatemail".

Accusing an entire community of people of hate, for the actions of a single one, is not nice at all, especially, when it is done without evidence, with just vague descriptions.

Have you considered, that in all these, it may be the V developers, that are in the minority???

> Bounds checking

    fn main() {
        x := []&int { len: 10, cap: 0 }
        println(x[4])
    }

Again, a bug caused by the auto generated string conversion method for arrays of pointers, that does not check for nil pointers. Once https://github.com/vlang/v/issues/14786 is fixed, that will work too.

It has nothing to do with bounds checking, as you can see if you just use `x := []int { len: 10, cap: 0 }` instead.

> Allowing the user to control the len property is a really bad idea.

Can you clarify what you mean by that?