This is important I think. Can help reduce ambiguity for any contributors. I'd like to help if you all think we should do this.

V already has https://vlang.io/docs.

I was talking about more of a language spec. With technical description of grammar and implementation details. Docs section is more of a language usage documentation

Ah. We have been talking about writing an extensive compiler specification. I'll pin this issue.

These are different things. @mseshachalam refers to language spec, you refer to compiler spec.

@medvednikov Do you think it would be good idea to start on this ? I am interested in working on this.

It might be good to require new features to the compiler to come with spec docs. The existing features can be documented over time (0.2 seems too ambitious and no one's volunteered, plus some features are probably still in flux).

Agreed about new compiler features to come with spec docs. With respect to existing ones, that was precisely the question. "starting" on it. Also, syntax-wise i think @medvednikov has already sort of finalized it. So, only implementation is under flux. My thought was that some type of formal documentation can help contributors to the compiler itself.

Yeah, I think that would be great, @spy16

I've also created an RFC repo: https://github.com/vlang/rfcs

Any thoughts on how to get started here? Golang language specification is simple and straightforward. But what about the file format ? are you expecting it to be in markdown or something else? @medvednikov

Does it make sense to write a spec at this point already? It sounds like a lot of features and syntax are still being discussed.

Might make more sense to extract a specification after 1.0, so the language can grow and settle organically until then?

I'd like to contribute a V to JavaScript compiler, it's better to have a relatively clear spec about the grammar