$ cd full-sample
# List notes mentioning "Channels" (main title).
$ zk list -q --debug-style --mention fwsj.md
>
Message passing 4oma.md (just now)
>
> - * A popular approach for safe concurrency is to use *message passing* instead of shared state.
> * Channels are an example of…
>
>Mutex inbox/er4k.md (just now)
>
> - …with a *locking system*.
> * Managing mutexes is tricky, using [channels](../fwsj) is an easier alternative.
> * The main risk is to…
>
>Concurrency in Rust g7qa.md (just now)
>
> - …a number of constructs for sharing data between threads:
> * [Channel](fwsj) for a safe [message passing](4oma) approach.
> * [Mutex](inbox/er4k…
>
# List notes mentioning "Dangling pointers" (using alias from the metadata).
$ zk list -q --debug-style --mention 3cut.md
>The borrow checker hkvy.md (just now)
>
> - …to the scope of the owned data to prevent dangling references. It also makes sure that the relationship between *lifetimes…
>
# List notes mentioned by "Message passing" (using the main title)
$ zk list -q --debug-style --mentioned-by 4oma.md
>Channel fwsj.md (just now)
>
> - * A popular approach for safe concurrency is to use *message passing* instead of shared state.
> * Channels are an example of…
>
>Do not communicate by sharing memory; instead, share memory by communicating ref/7fto.md (just now)
>
> - …advocating for this approach with their slogan: "[Do not communicate by sharing memory; instead, share memory by communicating](ref/7fto)".
>
> :programming:
>
# List notes mentioned by "The borrow checker" (using alias from the metadata)
$ zk list -q --debug-style --mentioned-by hkvy.md
>Dangling pointers 3cut.md (just now)
>
> - …to the scope of the owned data to prevent dangling references. It also makes sure that the relationship between *lifetimes…
>