The V Programming Language

Simple, fast, safe, compiled language for developing maintainable software 6.5k
Install V from source in 0.5 seconds
wget && gcc -o v v.c
Subscribe to development updates


V is a statically typed compiled programming language designed for building maintainable software.

It's similar to Go and is also influenced by Oberon, Rust, Swift.

V is a very simple language. Going through this documentation will take you about half an hour, and by the end of it you will learn pretty much the entire language.

Despite being simple, it gives a lot of power to the developer. Anything you can do in other languages, you can do in V.

Found an error/typo? Please submit a pull request.

Hello World

fn main() {
	println('hello world')

Functions are declared with fn. Return type goes after the function name. In this case main doesn't return anything, so the type is omitted.

Just like in C and all related languages, main is an entry point.

println is one of the few built-in functions. It prints the value to standard output.

fn main() declaration can be skipped in one file programs. This is useful when writing small programs, "scripts", or just learning the language. For brevity, fn main() will be skipped in this tutorial.

This means that a "hello world" program can be as simple as

println('hello world')


// This is a single line comment.

/* This is a multiline comment.
   /* It can be nested. */


fn main() {
	println(add(77, 33))
	println(sub(100, 50))

fn add(x int, y int) int {
	return x + y

fn sub(x, y int) int {
	return x - y

Again, the type comes after the argument's name.

Just like in Go and C, functions cannot be overloaded. This simplifies the code and improves maintainability and readability.

Functions can be used before their declaration: add and sub are declared after main, but can still be called from main. This is true for all declarations in V and eliminates the need of header files or thinking about the order of files and declarations.


name := 'Bob' 
age := 20
large_number := i64(9999999999)

Variables are declared and initialized with :=. This is the only way to declare variables in V. This means that variables always have an initial value.

The variable's type is inferred from the value on the right hand side. To force a different type, use type conversion: the expression T(v) converts the value v to the type T.

Unlike most other languages, V only allows defining variables in functions. Global (module level) variables are not allowed. There's no global state in V.


mut age := 20
age = 21

To change the value of the variable use =. In V, variables are immutable by default. To be able to change the value of the variable, you have to declare it with mut.

Try compiling the program above after removing mut from the first line.

Please note the difference between := and =
:= is used for declaring and initializing, = is used for assigning.


fn main() {
	age = 21

This code will not compile, because variable age is not declared. All variables need to be declared in V.


fn main() {
	age := 21

This code will not compile either, because unused variables result in a compilation error.


fn main() {
	a := 10 
	if true {
		a := 20

Unlike most languages, variable shadowing is not allowed. Declaring a variable with a name that is already used in a parent scope will result in a compilation error.

Basic types



i8  i16  i32  i64      i128 (soon)
u8  u16  u32  u64      u128 (soon) 

byte // alias for u8  
int  // alias for i32  
rune // alias for i32, represents a Unicode code point  

f32 f64

Please note that unlike C and Go, int is always a 32 bit integer.


name := 'Bob' 
println('Hello, $name!')  // `$` is used for string interpolation 

bobby := name + 'by' // + is used to concatenate strings 
println(bobby) // ==> "Bobby"  

println(bobby.substr(1, 3)) // ==> "ob"  
// println(bobby[1:3]) // This syntax will most likely replace the substr() method   

In V, a string is a read-only array of bytes. String data is encoded using UTF-8.

Both single and double quotes can be used to denote strings (TODO: double quotes are not supported yet). For consistency, vfmt converts double quotes to single quotes unless the string contains a single quote character.

Strings are immutable. This means that the substring function is very efficient: no copying is performed, no extra allocations required.


All operators in V must have values of the same type on both sides. This code will not compile if age is an int:

println('age = ' + age)
We have to either convert age to a string:
println('age = ' + age.str())
or use string interpolation (preferred):
println('age = $age')


nums := [1, 2, 3]
println(nums[1]) // ==> "2" 

mut names := ['John']
names << 'Peter' 
names << 'Sam' 
// names << 10  <-- This will not compile. `names` is an array of strings. 
println(names.len) // ==> "3" 
println('Alex' in names) // ==> "false" 

// We can also preallocate a certain amount of elements. 
nr_ids := 50
mut ids := [0 ; nr_ids] // This creates an array with 50 zeroes 

Array type is determined by the first element: [1, 2, 3] is an array of ints
['a', 'b'] is an array of strings ([]string).

All elements must have the same type. [1, 'a'] will not compile.

<< is an operator that appends a value to the end of the array.

.len field returns the length of the array. Note, that it's a read-only field, and it can't be modified by the user. All exported fields are read-only by default in V.

val in array returns true if the array contains val.


mut m := map[string]int{} // Only maps with string keys are allowed for now  
m['one'] = 1
println(m['one']) // ==> "1"  
println(m['bad_key']) // ==> "0"  
// TODO: implement a way to check if the key exists 

numbers := { // TODO: this syntax is not implemented yet  
	'one': 1,
	'two': 2,


a := 10 
b := 20 
if a < b { 
	println('$a < $b') 
} else if a > b { 
	println('$a > $b') 
} else { 
	println('$a == $b') 

if statements are pretty straightforward and similar to most other languages.

Unlike other C-like languages, there are no parentheses surrounding the condition, and the braces are always required.

if can be used as an expression:

num := 777
s := if num % 2 == 0 {
else {
println(s) // ==> "odd"

In operator

in allows to check whether an array contains an element.
nums := [1, 2, 3]
println(1 in nums) // ==> true 
It's also useful for writing more clear and compact boolean expressions:
if parser.token == .plus || parser.token == .minus || parser.token == .div || parser.token == .mult {

if parser.token in [.plus, .minus, .div, .mult] {
V optimizes such expressions, so both if statements above produce the same machine code, no arrays are created.

For loop

V has only one looping construct: for.
numbers := [1, 2, 3, 4, 5]
for num in numbers {
names := ['Sam', 'Peter']
for i, name in names {
	println('$i) $name')  // Output: 0) Sam
}                             //         1) Peter

The for .. in loop is used for going through elements of an array. If an index is required, an alternative form for index, value in can be used.


mut sum := 0
mut i := 0
for i <= 100 {
	sum += i
println(sum) // ==> "5050" 

This form of the loop is similar to while loops in other languages.

The loop will stop iterating once the boolean condition evaluates to false.

Again, there are no parentheses surrounding the condition, and the braces are always required.


mut num := 0
for {
	if num >= 10 {
println(num) // ==> "10" 

The condition can be omitted, this results in an infinite loop.


for i := 0; i < 10; i++ {

Finally, there's the traditional C style for loop. It's safer than the `while` form because with the latter it's easy to forget to update the counter and get stuck in an infinite loop.

Here i doesn't need to be declared with mut since it's always going to be mutable by definition.


os := 'windows' 
print('V is running on ')
switch os {
case 'darwin':
case 'linux':
// TODO: replace with match expressions 

A switch statement is a shorter way to write a sequence of if - else statements. It runs the first case whose value is equal to the condition expression.

Unlike C, break statement is not needed at the end of every block.


struct Point {
	x int
	y int 

p := Point{
	x: 10 
	y: 20 
println(p.x) // Struct fields are accessed using a dot 


Structs are allocated on the stack. To allocate a struct on the heap and get a pointer to it, use the & prefix:

pointer := &Point{10, 10}  // Alternative initialization syntax for structs with 3 fields or fewer
println(pointer.x) // Pointers have the same syntax for accessing fields  


V doesn't have subclassing, but it supports embedded structs:

// TODO: this will be implemented later in June
struct Button {
	title string

button := new_button('Click me')
button.set_pos(x, y)

// Without embedding we'd have to do

Access modifiers

Struct fields are private and immutable by default (making structs immutable as well). Their access modifiers can be changed with pub and mut. In total, there are 5 possible options:

struct Foo {
	a int     // private immutable (default) 
	b int     // private mutable 
	c int     // (you can list multiple fields with the same access modifier)   
	d int     // public immmutable (readonly) 
pub mut: 
	e int     // public, but mutable only in parent module  
pub mut mut: 
	f int 	  // public and mutable both inside and outside parent module  
}                 // (not recommended to use, that's why it's so verbose) 


For example, here's the string type defined in the builtin module:

struct string {
	str byteptr
	len int

It's easy to see from this definition that string is an immutable type.

The byte pointer with the string data is not accessible outside builtin at all. len field is public, but not mutable.

fn main() {
	str := 'hello' 
	len := str.len // OK  
	str.len++      // Compilation error  


struct User {
	age int 

fn (u User) can_register() bool {
	return u.age > 16 

user := User{age: 10} 
println(user.can_register()) // ==> "false"  

user2 := User{age: 20} 
println(user2.can_register()) // ==> "true"  

V doesn't have classes. But you can define methods on types.

A method is a function with a special receiver argument.

The receiver appears in its own argument list between the fn keyword and the method name.

In this example, the can_register method has a receiver of type User named u. The convention is not to use receiver names like self or this, but a short, preferably one letter long, name.

Pure functions by default

V functions are pure by default, meaning that their return values are only determined by their arguments, and their evaluation has no side effects.

This is achieved by lack of global variables and all function arguments being immutable by default, even when references are passed.

V is not a pure functional language however. It is possible to modify function arguments by using the same keyword mut:

struct User {
	is_registered bool 

fn (u mut User) register() {
	u.is_registered = true 

mut user := User{} 
println(user.is_registered) // ==> "false"  
println(user.is_registered) // ==> "true"  

In this example, the receiver (which is simply the first argument) is marked as mutable, so register() can change the user object. The same works with non-receiver arguments:

fn multiply_by_2(arr mut []int) {
	for i := 0; i < arr.len; i++ {
		arr[i] *= 2

mut nums := [1, 2, 3]
multiply_by_2(mut nums)
println(nums) // ==> "[2, 4, 6]"

Note, that you have to add mut before nums when calling this function. This makes it clear that the function being called will modify the value.

It is preferable to return values instead of modifying arguments. Modifying arguments should only be done in performance-critical parts of your application to reduce allocations and copying.

Use user.register() or user = register(user) instead of register(mut user).

V makes it easy to return a modifed version of an an object:

fn register(u User) User { 
	return { u | is_registered: true } 

user = register(user) 


const (
	PI    = 3.14
	World = '世界'


Constants are declared with const. They can only be defined at the module level (outside of functions).

Constant names must be capitalized. This helps distinguish them from variables.

Constant values can never be changed.

V constants are more flexible than in most languages. You can assign more complex values:

struct Color {
        r int
        g int
        b int

fn (c Color) str() string { return '{$c.r, $c.g, $c.b}' }

fn rgb(r, g, b int) Color { return Color{r: r, g: g, b: b} }

const (
        Numbers = [1, 2, 3]

        Red  = Color{r: 255, g: 0, b: 0}
        Blue = rgb(0, 0, 255)


Global variables are not allowed, so this can be really useful.


V is a very modular language. Creating reusable modules is encouraged and is very simple. To create a new module, create a directory with your module's name and .v files with code:
cd ~/code/modules
mkdir mymodule
vim mymodule/mymodule.v

// mymodule.v
module mymodule

// To export a function we have to use `pub`
pub fn say_hi() {
	println('hello from mymodule!')
You can have as many .v files in mymodule/ as you want.

Build it with v -lib ~/code/modules/mymodule.

That's it, you can now use it in your code:

module main

import mymodule

fn main() {

Note that you have to specify the module every time you call an external function. This may seem verbose at first, but it makes code much more readable and easier to understand, since it's always clear which function from which module is being called. Especially in large code bases.

Module names should be short, under 10 characters. Circular imports are not allowed.

You can create modules anywhere.

All modules are compiled statically into a single executable.


struct Dog {}
struct Cat {}

fn (d Dog) speak() string { 
	return 'woof'

fn (c Cat) speak() string { 
	return 'meow' 

interface Speaker {
	speak() string

fn perform(s Speaker) { 

dog := Dog{} 
cat := Cat{} 
perform(dog) // ==> "woof" 
perform(cat) // ==> "meow" 

A type implements an interface by implementing its methods. There is no explicit declaration of intent, no "implements" keyword.


enum Color {
	red green blue 

mut color :=
// V knows that `color` is a `Color`. No need to use `` here.
color = .green 
println(color) // ==> "1"  TODO: print "green"?  

Option/Result types & error handling

struct User {
	id int 
	name string

struct Repo {
	users []User 

fn new_repo() Repo {
	return Repo {
		users: [User{1, 'Andrew'}, User {2, 'Bob'}, User {10, 'Charles'}]

fn (r Repo) find_user_by_id(id int) ?User { 
	for user in r.users {
		if == id {
			// V automatically wraps this into an option type  
			return user 
	return error('User $id not found') 

fn main() {
	repo := new_repo() 
	user := repo.find_user_by_id(10) or { // Option types must be handled by `or` blocks  
		return  // `or` block must end with `return`, `break`, or `continue`  
	println( // ==> "10"  
	println( // ==> 'Charles'

V combines Option and Result into one type, so you don't need to decide which one to use.

The amount of work required to "upgrade" a function to an optional function is minimal: you have to add a ? to the return type and return an error when something goes wrong.

If you don't need to return an error, you can simply return None. (TODO: None is not implemented yet).

This is the primary way of handling errors in V. They are still values, like in Go, but the advantage is that errors can't be unhandled, and handling them is a lot less verbose.

You can also propagate errors:

resp := http.get(url)?
http.get returns ?http.Response. It was called with ?, so the error is propagated to the calling function or in case of main leads to a panic.

Basically the code above is a shorter version of

resp := http.get(url) or {

Generics (July)

struct Repo⟨T⟩ {
	db DB

fn new_repo⟨T⟩(db DB) Repo⟨T⟩ {
	return Repo⟨T⟩{db: db}

// This is a generic function. V will generate it for every type it's used with. 
fn (r Repo⟨T⟩) find_by_id(id int) ?T {  
	table_name := // in this example getting the name of the type gives us the table name 
	return r.db.query_one⟨T⟩('select * from $table_name where id = ?', id)

db := new_db()
users_repo := new_repo⟨User⟩(db)
posts_repo := new_repo⟨Post⟩(db)
user := users_repo.find_by_id(1)? 
post := posts_repo.find_by_id(1)? 
For readability, ⟨⟩ are allowed instead of <>. vfmt automatically replaces <> with ⟨⟩.


The concurrency model is very similar to Go. To run foo() concurrently, just call it with go foo(). Right now, it launches the function in a new system thread. Soon goroutines and the scheduler will be implemented.

Decoding JSON

struct User {
	name string
	age  int 
	foo  Foo    [skip]  // Use `skip` attribute to skip certain fields 

data := '{ "name": "Frodo", "age": 25 }'
user := json.decode(User, data) or {
	eprintln('Failed to decode json')

JSON is very popular nowadays, that's why JSON support is built in.

The first argument of the json.decode function is the type to decode to. The second argument is the JSON string.

V generates code for JSON encoding and decoding. No runtime reflection is used. This results in much better performance.


// hello.v 
fn hello() string {
	return 'Hello world'

// hello_test.v 
fn test_hello() {
    assert hello() == 'Hello world'
All test functions have to be placed in *_test.v files and begin with test_. To run the tests do v hello_test.v. To test an entire module, do v test mymodule.

Memory management

There's no garbage collection or reference counting. V cleans up what it can during compilation. For example:
fn draw_text(s string, x, y int) {

fn draw_scene() {
	draw_text('hello $name1', 10, 10)
	draw_text('hello $name2', 100, 10)
	draw_text(strings.repeat('X', 10000), 10, 50)
The strings don't escape draw_text, so they are cleaned up when the function exits.

In fact, the first two calls won't result in any allocations at all. These two strings are small, V will use a preallocated buffer for them.

For more complex cases manual memory management is required. This will be fixed soon.

V will detect memory leaks at runtime and report them. To clean up, for example, an array, use the free() method:

numbers := [0; 1000000] 





Advanced Topics

Calling C functions from V

#flag -lsqlite3

#include "sqlite3.h"

struct C.sqlite3 
struct C.sqlite3_stmt 

fn C.sqlite3_column_int(C.sqlite_stmt, int) int 

fn main() {
	path := 'sqlite3_users.db' 
	db := &C.sqlite3{} 
	C.sqlite3_open(path.cstr(), &db)

	query := 'select count(*) from users' 
	stmt := &C.sqlite3_stmt{} 
	C.sqlite3_prepare_v2(db, query.cstr(), - 1, &stmt, 0)
	nr_users := C.sqlite3_column_int(res, 0)

Compile time if

$if windows {
$if linux {
$if mac {
Compile time if starts with a $. Right now it can only be used to detect an OS.

Reflection via codegen

Having built-in JSON support is nice, but V also allows you to create efficient serializers for anything:
// TODO: planned in June
fn decode<T>(data string) T {
        mut result := T{}
        for field in T.fields {
                if field.typ == 'string' {
                        result.$field = get_string(data,
                } else if field.typ == 'int' {
                        result.$field = get_int(data,
        return result

// generates to:
fn decode_User(data string) User {
        mut result := User{} = get_string(data, 'name')
        result.age = get_int(data, 'age')
        return result

Limited operator overloading

struct Vec {
	x int
	y int

fn (a Vec) str() string { 
	return '{$a.x, $a.y}' 

fn (a Vec) + (b Vec) Vec {
	return Vec {
		a.x + b.x, 
		a.y + b.y 

fn (a Vec) - (b Vec) Vec {
	return Vec {
		a.x - b.x, 
		a.y - b.y

fn main() { 
	a := Vec{2, 3}
	b := Vec{4, 5}
	println(a + b) // ==> "{6, 8}"  
	println(a - b) // ==> "{-2, -2}"  

Operator overloading goes against V's philosophy of simplicity and predictability. But since scientific and graphical applications are among V's domains, operator overloading is very important to have in order to improve readability:

a.add(b).add(c.mul(d)) is a lot less readable than a + b + c * d.

To improve safety and maintainability, operator overloading has several limitations:

- It's only possible to overload +, -, *, / operators.
- Calling other functions inside operator functions is not allowed.
- Operator functions can't modify their arguments.
- Both arguments must have the same type (just like with all operators in V).

Translating C/C++ to V

TODO: translating C to V will be available in June. C++ to V will be available later this year.

V can translate your C/C++ code to human readable V code. Let's create a simple program test.cpp first:

#include <vector>
#include <string>
#include <iostream>

int main() {
        std::vector<std::string> s;
        s.push_back("V is ");
        std::cout << s.size() << std::endl;
        return 0;
Run v translate test.cpp and V will generate test.v:
fn main {
        mut s := []
	s << 'V is '
	s << 'awesome'

An online C/C++ to V translator is coming soon.

When should you translate C code and when should you simply call C code from V?

If you have well-written, well-tested C code, then of course you can always simply call this C code from V.

Translating it to V gives you several advantages:

- If you plan to develop that code base, you now have everything in one language, which is much safer and easier to develop in that C.

- Cross-compilation becomes a lot easier. You don't have to worry about it at all.

- No more build flags and include files either.

Hot code reloading


Cross compilation

To cross compile your project simply run
v -os windows .
v -os linux .
(Cross compiling for macOS is temporarily not possible.)

If you don't have any C dependencies, that's all you need to do. This works even when compiling GUI apps using the ui module or graphical apps using gg.

Cross-platform shell scripts in V

(Coming later in June.)

V can be used as an alternative to Bash to write deployment scripts, build scripts, etc.

The advantage of using V for this is the simplicity and predictability of the language, and cross-platform support. "V scripts" run on Unix-like systems as well as on Windows.

Start your program with a #v directive. It will make all functions in the os module global (so that you can use ls() instead of, for example).


// Same as:  
for file in ls('build/') {

mv('*.v', 'build/') 
// Same as:  
for file in ls('.') {
	if file.ends_with('.v') { 
		mv(file, 'build/') 
Now you can either compile this like a normal V program and get an executable you can deploy and run anywhere: v deploy.v && ./deploy

Or just run it more like a traditional bash script: v run deploy.v

Appendix I: Keywords

V has 22 keywords:

Appendix II: Operators

+    sum                    integers, floats, strings
-    difference             integers, floats 
*    product                integers, floats 
/    quotient               integers, floats 
%    remainder              integers

&    bitwise AND            integers
|    bitwise OR             integers
^    bitwise XOR            integers

<<   left shift             integer << unsigned integer
>>   right shift            integer >> unsigned integer 

Precedence    Operator
    5             *  /  %  <<  >>  & 
    4             +  -  |  ^
    3             ==  !=  <  <=  >  >=
    2             &&
    1             || 

Assignment Operators 
+=   -=   *=   /=   %=
&=   |=   ^=
>>=  <<=