vieter-v
/
v
2
0
Fork 0
Code Issues Pull Requests Releases Activity

doc: autofree/gc update

master
Alexander Medvednikov 2022-06-11 20:44:28 +03:00 committed by GitHub
parent f3351b6a29
commit f08266ab66
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/docs.md
View File

@ -4114,17 +4114,16 @@ fn (data &MyType) free() {
Just as the compiler frees C data types with C's `free()`, it will statically insert Just as the compiler frees C data types with C's `free()`, it will statically insert
`free()` calls for your data type at the end of each variable's lifetime. `free()` calls for your data type at the end of each variable's lifetime.
Autofree can be enabled with an `-autofree` flag.
For developers willing to have more low level control, autofree can be disabled with For developers willing to have more low level control, autofree can be disabled with
`-manualfree`, or by adding a `[manualfree]` on each function that wants manage its `-manualfree`, or by adding a `[manualfree]` on each function that wants manage its
memory manually. (See [attributes](#attributes)). memory manually. (See [attributes](#attributes)).
_Note: right now autofree is hidden behind the -autofree flag. It will be enabled by
default in V 0.3. If autofree is not used, V programs will leak memory._
Note 2: Autofree is still WIP. Until it stabilises and becomes the default, please Note 2: Autofree is still WIP. Until it stabilises and becomes the default, please
compile your long running processes with `-gc boehm`, which will use the avoid using it. Right now allocations are handled by a minimal and well performing GC
Boehm-Demers-Weiser conservative garbage collector, to free the memory, that your until V's autofree engine is production ready.
programs leak, at runtime.
### Examples ### Examples