Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. https://vlang.io
 
 
Go to file
Alexander Medvednikov e8f8defc3e ast: SqlExpr 2020-06-16 12:14:22 +02:00
.ctags.d v.ctags: improve detection of `mut x :=` 2020-04-30 20:20:48 +03:00
.github ci: disable linux cross compilation test for now 2020-06-16 00:52:07 +02:00
cmd vlib: fix os.exec().output usages, that may rely on trimmed lines 2020-06-15 15:38:20 +03:00
doc doc: use `v new` instead of `v create` 2020-06-14 21:20:31 +03:00
examples examples: add overflow protection in path_tracing.v, fix randomization 2020-06-15 19:56:19 +03:00
thirdparty sokol: fullscreen linux 2020-06-14 23:36:36 +02:00
tutorials tutorials: switch to `mut f Foo` 2020-05-24 21:27:14 +03:00
vlib ast: SqlExpr 2020-06-16 12:14:22 +02:00
.editorconfig cgen: enum str() 2020-04-08 15:54:38 +02:00
.gitattributes vfmt2: more convenient way to test multiple files for correct formatting 2020-02-18 17:54:14 +01:00
.gitignore tcc: support tcc on Windows 2020-06-14 23:15:12 +02:00
0.2_roadmap.txt Revert "term: make compilable with v2 on windows" 2020-03-20 21:15:45 +01:00
BSDmakefile freebsd: fix BSDmakefile 2019-12-18 14:13:43 +03:00
CHANGELOG.md changelog: fix a typo 2020-05-10 16:24:43 +02:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2019-10-06 04:43:48 +03:00
CONTRIBUTING.md doc: fix line breaks to make it 80 characters / line 2020-05-29 03:05:04 +02:00
Dockerfile dockerfile: fix build failure 2019-09-13 01:19:57 +03:00
Dockerfile.alpine cmd/v: rewrite flags 2020-03-06 18:53:29 +01:00
Dockerfile.cross move v.v to cmd/v 2020-02-09 10:08:04 +01:00
LICENSE update copyright year 2020-01-23 21:04:46 +01:00
Makefile make: optimize Makefile 2020-06-02 19:11:58 +03:00
README.md readme: glfw is no longer needed 2020-06-09 14:45:55 +02:00
make.bat make.bat: add `-local flag 2020-06-04 14:07:02 +02:00
v.mod v.mod: add repo_url attribute too 2020-06-03 11:58:14 +03:00

README.md

The V Programming Language

vlang.io | Docs | Changelog | Speed | Contributing

Build Status Sponsor Patreon Discord Twitter

Key Features of V

  • Simplicity: the language can be learned in less than an hour
  • Fast compilation: ≈100k — 1.2 million loc/s
  • Easy to develop: V compiles itself in less than a second
  • Performance: within 3% of C
  • Safety: no null, no globals, no undefined behavior, immutability by default
  • C to V translation
  • Hot code reloading
  • Cross-platform UI library
  • Built-in graphics library
  • Easy cross compilation
  • REPL
  • Built-in ORM
  • C and JavaScript backends

A stable 0.2 release is planned for June 2020. Right now V is in an alpha stage.

Installing V from source

Linux, macOS, Windows, *BSD, Solaris, WSL, Android, Raspbian

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

That's it! Now you have a V executable at [path to V repo]/v. [path to V repo] can be anywhere.

(On Windows make means running make.bat, so make sure you use cmd.exe)

Now you can try ./v run examples/hello_world.v (v.exe on Windows).

V is being constantly updated. To update V, simply run:

v up

C compiler

You'll need Clang or GCC or Visual Studio. If you are doing development, you most likely already have one of those installed.

Otherwise, follow these instructions:

Symlinking

NB: it is highly recommended, that you put V on your PATH. That saves you the effort to type in the full path to your v executable everytime. V provides a convenience v symlink command to do that more easily.

On Unix systems, it creates a /usr/local/bin/v symlink to your executable. To do that, run:

sudo ./v symlink

On Windows, start a new shell with administrative privileges, for example by Windows Key, then type cmd.exe, right click on its menu entry, and choose Run as administrator. In the new administrative shell, cd to the path, where you have compiled v.exe, then type:

.\v.exe symlink

That will make v available everywhere, by adding it to your PATH. Please restart your shell/editor after that, so that it can pick the new PATH variable.

NB: there is no need to run v symlink more than once - v will continue to be available, even after v up, restarts and so on. You only need to run it again, if you decide to move the V repo folder somewhere else.

Docker

Expand Docker instructions
git clone https://github.com/vlang/v
cd v
docker build -t vlang .
docker run --rm -it vlang:latest
v

Docker with Alpine/musl:

git clone https://github.com/vlang/v
cd v
docker build -t vlang --file=Dockerfile.alpine .
docker run --rm -it vlang:latest
/usr/local/v/v

Testing and running the examples

Make sure V can compile itself:

v -o v2 cmd/v
$ v
V 0.1.x
Use Ctrl-C or `exit` to exit

>>> println('hello world')
hello world
>>>
cd examples
v hello_world.v && ./hello_world    # or simply
v run hello_world.v                 # this builds the program and runs it right away

v word_counter.v && ./word_counter cinderella.txt
v run news_fetcher.v
v run tetris/tetris.v

In order to build Tetris and anything else using the graphics module on non-Windows systems, you will need to install freetype libraries.

If you plan to use the http package, you also need to install OpenSSL on non-Windows systems.

macOS:
brew install freetype openssl

Debian/Ubuntu:
sudo apt install libfreetype6-dev libssl-dev

Arch/Manjaro:
sudo pacman -S freetype2

Fedora:
sudo dnf install freetype-devel

V UI

https://github.com/vlang/ui

Troubleshooting

Please see the Troubleshooting section on our wiki page