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

docs: remove & from shared initializers (#8499)

This commit is contained in:
Uwe Krüger 2021-02-01 21:43:45 +01:00 committed by GitHub
parent 51f2eb81f4
commit 8bf3fe5d48
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 6 deletions

View File

@ -2655,7 +2655,7 @@ fn (shared b St) g() {
}
fn main() {
shared a := &St{ // create as reference so it's on the heap
shared a := St{
x: 10
}
go a.g()
@ -2665,6 +2665,7 @@ fn main() {
}
}
```
Shared variables must be structs, arrays or maps.
## Decoding JSON

View File

@ -131,12 +131,12 @@ fn i(atomic x u64) {...}
a := St{...}
f(a)
mut b := &St{...} // reference since transferred to coroutine
mut b := St{...}
f(b)
go g(mut b)
// `b` should not be accessed here any more
shared c := &St{...}
shared c := St{...}
h(shared c)
atomic d &u64
@ -146,7 +146,7 @@ i(atomic d)
Inside a `lock c {...}` block `c` behaves like a `mut`,
inside an `rlock c {...}` block like an immutable:
```v ignore
shared c := &St{...}
shared c := St{...}
lock c {
g(mut c)
f(c)
@ -166,14 +166,14 @@ block. However in simple and obvious cases the necessary lock/unlock
can be generated automatically for `array`/`map` operations:
```v ignore
shared a []int{...}
shared a := []int{cap: 5}
go h2(shared a)
a << 3
// keep in mind that `h2()` could change `a` between these statements
a << 4
x := a[1] // not necessarily `4`
shared b map[string]int
shared b := map[string]int{}
go h3(shared b)
b['apple'] = 3
c['plume'] = 7