Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. https://vlang.io
[![Sponsor][SponsorBadge]][SponsorUrl] [![Patreon][PatreonBadge]][PatreonUrl] [![Discord][DiscordBadge]][DiscordUrl] [![Twitter][TwitterUrl]][TwitterBadge]
Despite being at an early development stage, the V language is relatively stable and has backwards compatibility guarantee, meaning that the code you write today is guaranteed to work a month, a year, or five years from now.
There still may be minor syntax changes before the 1.0 release, but they will be handled automatically via
vfmt, as has been done in the past.
The V core APIs (primarily the
osmodule) will still have minor changes until they are stabilized in V 1.0. Of course the APIs will grow after that, but without breaking existing code.
Unlike many other languages, V is not going to be always changing, with new features being introduced and old features modified. It is always going to be a small and simple language, very similar to the way it is right now.
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.
make.bat, so make sure you use
Now you can try
./v run examples/hello_world.v(
V is constantly being updated. To update V, simply run:
It's recommended to use Clang, GCC, or Visual Studio. If you are doing development, you most likely already have one of those installed.
Otherwise, follow these instructions:
However, if none is found when running
makeon Linux or Windows, TCC is downloaded as the default C backend. It's very lightweight (several MB) so this shouldn't take too long.
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 every time. V provides a convenience
v symlinkcommand to do that more easily.
On Unix systems, it creates a
/usr/local/bin/vsymlink 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:
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 symlinkmore 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.
git clone https://github.com/vlang/v cd v docker build -t vlang . docker run --rm -it vlang:latest
git clone https://github.com/vlang/v cd v docker build -t vlang --file=Dockerfile.alpine . docker run --rm -it vlang:latest
Make sure V can compile itself:
$ v V 0.2.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 run word_counter/word_counter.v word_counter/cinderella.txt v run news_fetcher.v v run tetris/tetris.v
NB: In order to build Tetris or 2048 (or anything else using
gggraphics modules) on some Linux systems, you need to install
If you plan to use the http package, you also need to install OpenSSL on non-Windows systems.
macOS: brew install openssl
Debian/Ubuntu: sudo apt install libssl-dev
Arch/Manjaro: openssl is installed by default
Fedora: sudo dnf install openssl-devel
syncmodule and channel implementation uses libatomic. It is most likely already installed on your system, but if not, you can install it, by doing the following: ```bash MacOS: already installed
Debian/Ubuntu: sudo apt install libatomic1
Fedora/CentOS/RH: sudo dnf install libatomic-static ```
vabtool, building V UI and graphical apps for Android can become as easy as:
Check out the Building a simple web blog tutorial and Gitly, a light and fast alternative to GitHub/GitLab: