TheCloud/v
1
0
Fork 0
mirror of https://github.com/vlang/v.git synced 2025-09-17 03:17:25 -04:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix minor typos in the memory management section (#22151)

Browse Source
This commit is contained in:
Kim Shrier 2024-09-02 22:51:03 -06:00 committed by GitHub
parent b898987ece
commit 0a61b4a076
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/docs.md
View File

@ -4851,7 +4851,7 @@ Just as the compiler frees C data types with C's `free()`, it will statically in
Autofree can be enabled with an `-autofree` flag.
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 to manage its
memory manually. (See [attributes](#attributes)).
> [!NOTE]
@ -4963,7 +4963,7 @@ Here `a` is stored on the stack since its address never leaves the function `f()
However a reference to `b` is part of `e` which is returned. Also a reference to
`c` is returned. For this reason `b` and `c` will be heap allocated.
Things become less obvious when a reference to an object is passed as function argument:
Things become less obvious when a reference to an object is passed as a function argument:
```v
struct MyStruct {