1
0
mirror of https://github.com/vlang/v.git synced 2023-08-10 21:13:21 +03:00
v/README.md

377 lines
14 KiB
Markdown
Raw Normal View History

<div align="center" style="display:grid;place-items:center;">
2020-04-19 21:46:18 +03:00
<p>
<a href="https://vlang.io/" target="_blank"><img width="80" src="https://raw.githubusercontent.com/vlang/v-logo/master/dist/v-logo.svg?sanitize=true" alt="V logo"></a>
2020-04-13 06:11:56 +03:00
</p>
2020-04-19 21:46:18 +03:00
<h1>The V Programming Language</h1>
2019-06-22 21:22:41 +03:00
2022-05-04 18:06:41 +03:00
[vlang.io](https://vlang.io) | [Docs](https://github.com/vlang/v/blob/master/doc/docs.md) | [Changelog](https://github.com/vlang/v/blob/master/CHANGELOG.md) | [Speed](https://fast.vlang.io/) | [Contributing & compiler design](https://github.com/vlang/v/blob/master/CONTRIBUTING.md)
2020-04-13 06:11:56 +03:00
</div>
<div align="center" style="display:grid;place-items:center;">
<!--
2020-04-19 21:46:18 +03:00
[![Build Status][WorkflowBadge]][WorkflowUrl]
-->
[![Sponsor][SponsorBadge]][SponsorUrl]
[![Patreon][PatreonBadge]][PatreonUrl]
[![Discord][DiscordBadge]][DiscordUrl]
[![Twitter][TwitterBadge]][TwitterUrl]
[![Modules][ModulesBadge]][ModulesUrl]
2020-04-13 06:11:56 +03:00
</div>
2019-06-22 21:22:41 +03:00
2019-06-24 17:04:19 +03:00
## Key Features of V
2023-02-13 11:29:02 +03:00
2023-03-03 09:28:07 +03:00
- Simplicity: the language can be learned over the course of a weekend
2021-04-08 03:31:52 +03:00
- Fast compilation: ≈110k loc/s with a Clang backend,
2023-02-13 11:29:02 +03:00
≈500k loc/s with native and tcc backends *(Intel i5-7500, SSD, no
optimization)* ([demo video](https://www.youtube.com/watch?v=pvP6wmcl_Sc))
2019-06-24 17:07:41 +03:00
- Easy to develop: V compiles itself in less than a second
- Performance: as fast as C (V's main backend compiles to human-readable C)
2023-02-28 11:55:57 +03:00
- Safety: no null, no globals, no undefined behavior (wip), immutability by default
2022-06-23 02:33:09 +03:00
- C to V translation ([Translating DOOM demo video](https://www.youtube.com/watch?v=6oXrz3oRoEg))
2019-06-24 17:36:30 +03:00
- Hot code reloading
2023-02-28 11:58:52 +03:00
- [Flexible memory management](https://vlang.io/#memory). GC by default, manual via `v -gc none`,
arena allocation via `v -prealloc`, autofree via `v -autofree`
([autofree demo video](https://www.youtube.com/watch?v=gmB8ea8uLsM)).
2020-01-12 22:30:21 +03:00
- [Cross-platform UI library](https://github.com/vlang/ui)
- Built-in graphics library
- Easy cross-compilation
2019-06-24 17:04:19 +03:00
- REPL
2020-08-11 02:07:17 +03:00
- [Built-in ORM](https://github.com/vlang/v/blob/master/doc/docs.md#orm)
- [Built-in web framework](https://github.com/vlang/v/blob/master/vlib/vweb/README.md)
2019-09-07 14:50:12 +03:00
- C and JavaScript backends
- Great for writing low-level software ([Vinix OS](https://github.com/vlang/vinix))
2019-06-24 17:04:19 +03:00
2020-06-30 21:04:56 +03:00
## Stability guarantee and future changes
2023-02-13 11:29:02 +03:00
2020-06-30 21:04:56 +03:00
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 `os` module) will still have minor changes until
2021-04-20 15:46:47 +03:00
they are stabilized in V 1.0. Of course the APIs will grow after that, but without breaking
2020-06-30 21:04:56 +03:00
existing code.
Unlike many other languages, V is not going to be always changing, with new features
2020-08-06 18:23:54 +03:00
being introduced and old features modified. It is always going to be a small and simple
2020-06-30 21:04:56 +03:00
language, very similar to the way it is right now.
2022-11-02 08:26:57 +03:00
## Installing V from source
--> **_(this is the preferred method)_**
2019-06-22 21:22:41 +03:00
### Linux, macOS, Windows, *BSD, Solaris, WSL, etc.
2023-02-13 11:29:02 +03:00
2023-03-03 09:28:07 +03:00
Usually, installing V is quite simple if you have an environment that already has a
functional `git` installation.
To get started, simply try to execute the following in your terminal/shell:
2023-02-13 11:29:02 +03:00
2019-06-22 21:22:41 +03:00
```bash
git clone https://github.com/vlang/v
2019-06-29 13:58:52 +03:00
cd v
make
# HINT: Using Windows? run make.bat in a cmd shell, or ./make.bat in PowerShell
2019-06-26 00:02:25 +03:00
```
That should be it and you should find your V executable at `[path to V repo]/v`.
`[path to V repo]` can be anywhere.
(As in the hint above, on Windows `make` means running `make.bat`.)
2019-10-22 09:21:59 +03:00
Now you can try `./v run examples/hello_world.v` (or `v run examples/hello_world.v` in cmd shell).
* *Trouble? Please see the note above and link to
2023-02-13 11:29:02 +03:00
[Installation Issues](https://github.com/vlang/v/discussions/categories/installation-issues)
for help.*
2021-01-14 06:08:58 +03:00
V is constantly being updated. To update V, simply run:
2019-09-01 22:56:49 +03:00
2020-08-11 02:07:17 +03:00
```bash
2019-09-01 22:56:49 +03:00
v up
```
2023-02-13 11:29:02 +03:00
> **Note**
> If you run into any trouble, or you have a different operating
> system or Linux distribution that doesn't install or work immediately, please see
> [Installation Issues](https://github.com/vlang/v/discussions/categories/installation-issues)
2023-02-28 11:55:57 +03:00
> and search for your OS and problem.
2023-02-13 11:29:02 +03:00
>
2023-02-28 11:55:57 +03:00
> If you can't find your problem, please add it to an existing discussion if one exists for
2023-02-13 11:29:02 +03:00
> your OS, or create a new one if a main discussion doesn't yet exist for your OS.
2022-11-02 08:26:57 +03:00
### C compiler
2023-02-13 11:29:02 +03:00
The [Tiny C Compiler (tcc)](https://repo.or.cz/w/tinycc.git) is downloaded for you by `make` if
there is a compatible version for your system, and installed under the V `thirdparty` directory.
2023-02-13 11:29:02 +03:00
This compiler is very fast, but does almost no optimizations. It is best for development builds.
For production builds (using the `-prod` option to V), it's recommended to use clang, gcc, or
Microsoft Visual C++. If you are doing development, you most likely already have one of those
installed.
2019-10-05 15:59:34 +03:00
Otherwise, follow these instructions:
- [Installing a C compiler on Linux and macOS](https://github.com/vlang/v/wiki/Installing-a-C-compiler-on-Linux-and-macOS)
2019-09-01 23:15:47 +03:00
- [Installing a C compiler on Windows](https://github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows)
2019-09-01 22:56:49 +03:00
### Symlinking
2023-02-13 11:29:02 +03:00
> **Note**
> 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 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:
2019-06-22 21:22:41 +03:00
2019-10-15 09:03:21 +03:00
```bash
2019-09-11 15:32:40 +03:00
sudo ./v symlink
2019-06-22 21:22:41 +03:00
```
On Windows, start a new shell with administrative privileges, for example by pressing the
<kbd>Windows Key</kbd>, 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, then
type:
2020-08-11 02:07:17 +03:00
```bat
v symlink
```
2023-02-13 11:29:02 +03:00
(or `./v symlink` in PowerShell)
2020-08-11 02:07:17 +03:00
That will make V available everywhere, by adding it to your PATH. Please restart your
shell/editor after that, so that it can pick up the new PATH variable.
2023-02-13 11:29:02 +03:00
> **Note**
> There is no need to run `v symlink` more than once - v will still 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.
### Void Linux
2023-02-13 11:29:02 +03:00
<details><summary>Expand Void Linux instructions</summary>
```bash
# xbps-install -Su base-devel
# xbps-install libatomic-devel
$ git clone https://github.com/vlang/v
$ cd v
$ make
```
2023-02-13 11:29:02 +03:00
</details>
2019-08-27 04:17:50 +03:00
### Docker
2023-02-13 11:29:02 +03:00
2020-01-12 22:30:21 +03:00
<details><summary>Expand Docker instructions</summary>
2019-07-23 03:41:55 +03:00
```bash
git clone https://github.com/vlang/v
cd v
docker build -t vlang .
docker run --rm -it vlang:latest
```
2023-02-13 11:29:02 +03:00
2020-08-11 02:07:17 +03:00
### Docker with Alpine/musl
2023-02-13 11:29:02 +03:00
2019-11-28 11:46:52 +03:00
```bash
git clone https://github.com/vlang/v
cd v
docker build -t vlang --file=Dockerfile.alpine .
docker run --rm -it vlang:latest
```
2023-02-13 11:29:02 +03:00
2020-08-11 02:07:17 +03:00
</details>
2019-11-28 11:46:52 +03:00
### Termux/Android
2023-02-13 11:29:02 +03:00
On Termux, V needs some packages preinstalled - a working C compiler, also `libexecinfo`,
`libgc` and `libgc-static`. After installing them, you can use the same script, like on
Linux/macos:
2023-02-13 11:29:02 +03:00
```bash
pkg install clang libexecinfo libgc libgc-static make git
git clone https://github.com/vlang/v
cd v
make
```
## Editor/IDE Plugins
To bring IDE functions for the V programming languages to your editor, check out
[v-analyzer](https://github.com/v-analyzer/v-analyzer). It provides a
2023-07-29 15:27:03 +03:00
[VS Code extension](https://marketplace.visualstudio.com/items?itemName=VOSCA.vscode-v-analyzer)
and language server capabilities for other editors.
2023-07-29 15:27:03 +03:00
The plugin for JetBrains IDEs (IntelliJ, CLion, GoLand, etc.) also offers a great development
experience with V. You can find all features in [its documentation](https://plugins.jetbrains.com/plugin/20287-vlang/docs/syntax-highlighting.html).
Other Plugins:
- [Vim plugins](https://github.com/vlang/awesome-v#vim)
- [Emacs plugins](https://github.com/vlang/awesome-v#emacs)
- [Sublime Text 3 plugins](https://github.com/vlang/awesome-v#sublime-text-3)
- [Atom plugins](https://github.com/vlang/awesome-v#atom)
2022-07-04 15:33:41 +03:00
## Testing and running the examples
2023-02-13 11:29:02 +03:00
2019-08-12 10:54:35 +03:00
Make sure V can compile itself:
2023-02-13 11:29:02 +03:00
2019-10-15 09:03:21 +03:00
```bash
$ v self
2019-06-26 18:58:59 +03:00
$ v
V 0.3.x
Use Ctrl-C or `exit` to exit
2019-06-22 21:22:41 +03:00
>>> println('hello world')
hello world
>>>
```
2023-02-13 11:29:02 +03:00
2019-10-15 09:03:21 +03:00
```bash
2019-08-12 11:00:29 +03:00
cd examples
2019-06-26 19:04:10 +03:00
v hello_world.v && ./hello_world # or simply
v run hello_world.v # this builds the program and runs it right away
2019-06-22 21:22:41 +03:00
2021-04-14 08:51:32 +03:00
v run word_counter/word_counter.v word_counter/cinderella.txt
2019-06-24 18:13:02 +03:00
v run news_fetcher.v
2019-07-22 05:57:55 +03:00
v run tetris/tetris.v
2019-06-22 21:22:41 +03:00
```
2023-02-13 11:29:02 +03:00
<img src='https://raw.githubusercontent.com/vlang/v/master/examples/tetris/screenshot.png' width=300 alt='tetris screenshot'>
2019-06-23 17:16:55 +03:00
2023-02-13 11:29:02 +03:00
In order to build Tetris or 2048 (or anything else using `sokol` or `gg` graphics modules),
you will need additional development libraries for your system.
| System | Installation method |
|---------------------|----------------------------------------------------------------------------------------------------|
| Debian/Ubuntu based | `sudo apt install libxi-dev libxcursor-dev libgl-dev` |
| Fedora/RH/CentOS | `sudo dnf install libXcursor-devel libXi-devel libX11-devel libglvnd-devel` |
| NixOS | add `xorg.libX11.dev xorg.libXcursor.dev xorg.libXi.dev libGL.dev` to `environment.systemPackages` |
## V net.http, net.websocket, `v install`
2023-02-13 11:29:02 +03:00
The net.http module, the net.websocket module, and the `v install` command may all use SSL.
2023-02-13 11:29:02 +03:00
V comes with a version of mbedtls, which should work on all systems. If you find a need to
use OpenSSL instead, you will need to make sure that it is installed on your system, then
use the `-d use_openssl` switch when you compile.
To install OpenSSL on non-Windows systems:
2019-06-22 21:22:41 +03:00
| System | Installation command |
|---------------------|----------------------------------|
| macOS | `brew install openssl` |
| Debian/Ubuntu based | `sudo apt install libssl-dev` |
| Arch/Manjaro | openssl is installed by default |
| Fedora/CentOS/RH | `sudo dnf install openssl-devel` |
2019-06-24 19:53:22 +03:00
2023-02-13 11:29:02 +03:00
On Windows, OpenSSL is simply hard to get working correctly. The instructions
[here](https://tecadmin.net/install-openssl-on-windows/) may (or may not) help.
## V sync
2023-02-13 11:29:02 +03:00
V's `sync` module 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:
2023-02-13 11:29:02 +03:00
| System | Installation command |
|---------------------|-------------------------------------|
| macOS | already installed |
| Debian/Ubuntu based | `sudo apt install libatomic1` |
| Fedora/CentOS/RH | `sudo dnf install libatomic-static` |
2020-01-12 22:30:21 +03:00
## V UI
2023-02-13 11:29:02 +03:00
2020-01-12 22:30:21 +03:00
<a href="https://github.com/vlang/ui">
<img src='https://raw.githubusercontent.com/vlang/ui/master/examples/screenshot.png' width=712 alt='V UI example screenshot'>
2020-01-12 22:30:21 +03:00
</a>
https://github.com/vlang/ui
2019-12-12 20:22:11 +03:00
<!---
2019-09-15 04:10:12 +03:00
## JavaScript backend
[examples/hello_v_js.v](examples/hello_v_js.v):
2019-10-15 09:01:56 +03:00
```v
2019-09-15 04:10:12 +03:00
fn main() {
for i in 0 .. 3 {
println('Hello from V.js')
}
2019-09-15 04:10:12 +03:00
}
```
```bash
v -o hi.js examples/hello_v_js.v && node hi.js
2019-09-15 04:10:12 +03:00
Hello from V.js
Hello from V.js
Hello from V.js
```
2019-12-12 20:22:11 +03:00
-->
## Android graphical apps
2023-02-13 11:29:02 +03:00
With V's `vab` tool, building V UI and graphical apps for Android can become as easy as:
2023-02-13 11:29:02 +03:00
```
./vab /path/to/v/examples/2048
```
2023-02-13 11:29:02 +03:00
[https://github.com/vlang/vab](https://github.com/vlang/vab).
<img src="https://user-images.githubusercontent.com/768942/107622846-c13f3900-6c58-11eb-8a66-55db12979b73.png" alt="vab examples screenshot">
## Developing web applications
2023-02-13 11:29:02 +03:00
2023-02-28 11:55:57 +03:00
Check out the
2023-02-13 11:29:02 +03:00
[Building a simple web blog](https://github.com/vlang/v/blob/master/tutorials/building_a_simple_web_blog_with_vweb/README.md)
tutorial and Gitly, a light and fast alternative to GitHub/GitLab:
https://github.com/vlang/gitly
<img src="https://user-images.githubusercontent.com/687996/85933714-b195fe80-b8da-11ea-9ddd-09cadc2103e4.png" alt="gitly screenshot">
2021-08-16 06:34:13 +03:00
## Vinix, an OS/kernel written in V
2023-02-13 11:29:02 +03:00
V is great for writing low-level software like drivers and kernels.
2021-08-16 08:37:13 +03:00
Vinix is an OS/kernel that already runs bash, GCC, V, and nano.
2021-08-16 06:34:13 +03:00
https://github.com/vlang/vinix
<img src="https://github.com/vlang/vinix/blob/main/screenshot0.png?raw=true" alt="vinix screenshot 1">
<img src="https://github.com/vlang/vinix/blob/main/screenshot1.png?raw=true" alt="vinix screenshot 2">
2021-08-16 06:34:13 +03:00
## Acknowledgement
2023-02-13 11:29:02 +03:00
2023-02-28 11:55:57 +03:00
V thanks Fabrice Bellard for his original work on the
[TCC - Tiny C Compiler](https://bellard.org/tcc/).
Note the TCC website is old; the current TCC repository can be found
[here](https://repo.or.cz/w/tinycc.git).
V utilizes pre-built TCC binaries located at
2023-02-13 11:29:02 +03:00
[https://github.com/vlang/tccbin/](https://github.com/vlang/tccbin/).
## Troubleshooting
2023-02-13 11:29:02 +03:00
2023-02-28 11:55:57 +03:00
Please see the
[Troubleshooting](https://github.com/vlang/v/wiki/Troubleshooting)
section on our
2023-03-03 09:28:07 +03:00
[wiki page](https://github.com/vlang/v/wiki).
2020-04-19 21:46:18 +03:00
[WorkflowBadge]: https://github.com/vlang/v/workflows/CI/badge.svg
[DiscordBadge]: https://img.shields.io/discord/592103645835821068?label=Discord&logo=discord&logoColor=white
2022-11-02 08:26:57 +03:00
[PatreonBadge]: https://img.shields.io/endpoint.svg?url=https%3A%2F%2Fshieldsio-patreon.vercel.app%2Fapi%3Fusername%3Dvlang%26type%3Dpatrons&style=flat
2020-04-19 21:46:18 +03:00
[SponsorBadge]: https://camo.githubusercontent.com/da8bc40db5ed31e4b12660245535b5db67aa03ce/68747470733a2f2f696d672e736869656c64732e696f2f7374617469632f76313f6c6162656c3d53706f6e736f72266d6573736167653d254532253944254134266c6f676f3d476974487562
[TwitterBadge]: https://img.shields.io/badge/follow-%40v_language-1DA1F2?logo=twitter&style=flat&logoColor=white&color=1da1f2
[ModulesBadge]: https://img.shields.io/badge/modules-reference-027d9c?logo=v&logoColor=white&logoWidth=10
2020-04-19 21:46:18 +03:00
[WorkflowUrl]: https://github.com/vlang/v/commits/master
[DiscordUrl]: https://discord.gg/vlang
[PatreonUrl]: https://patreon.com/vlang
[SponsorUrl]: https://github.com/sponsors/medvednikov
[TwitterUrl]: https://twitter.com/v_language
[ModulesUrl]: https://modules.vlang.io