Fix indents in NEWS [ci skip]

The MarkDown parser in RDoc requires 4 columns indentation for
paragraphs following list items.  Otherwise, the following paragraphs
are not interpreted as the part of the preceeding list item,
This commit is contained in:
Nobuyoshi Nakada 2022-12-01 23:01:28 +09:00
parent 0436f1e15a
commit 01790de9e6
No known key found for this signature in database
GPG Key ID: 7CD2805BFA3770C6

30
NEWS.md
View File

@ -104,17 +104,19 @@ Note: We're only listing outstanding class updates.
* Fiber
* Introduce `Fiber.[]` and `Fiber.[]=` for inheritable fiber storage.
Introduce `Fiber#storage` and `Fiber#storage=` (experimental) for getting
and resetting the current storage. Introduce `Fiber.new(storage:)` for
setting the storage when creating a fiber. [[Feature #19078]]
* Introduce Fiber.[] and Fiber.[]= for inheritable fiber storage.
Introduce Fiber#storage and Fiber#storage= (experimental) for
getting and resetting the current storage. Introduce
`Fiber.new(storage:)` for setting the storage when creating a
fiber. [[Feature #19078]]
Existing Thread and Fiber local variables can be tricky to use. Thread
local variables are shared between all fibers, making it hard to isolate,
while Fiber local variables can be hard to share. It is often desirable
to define unit of execution ("execution context") such that some state
is shared between all fibers and threads created in that context. This is
what Fiber storage provides.
Existing Thread and Fiber local variables can be tricky to use.
Thread local variables are shared between all fibers, making it
hard to isolate, while Fiber local variables can be hard to
share. It is often desirable to define unit of execution
("execution context") such that some state is shared between all
fibers and threads created in that context. This is what Fiber
storage provides.
```ruby
def log(message)
@ -136,10 +138,10 @@ Note: We're only listing outstanding class updates.
end
```
You should generally consider Fiber storage for any state which you want
to be shared implicitly between all fibers and threads created in a given
context, e.g. a connection pool, a request id, a logger level,
environment variables, configuration, etc.
You should generally consider Fiber storage for any state which
you want to be shared implicitly between all fibers and threads
created in a given context, e.g. a connection pool, a request
id, a logger level, environment variables, configuration, etc.
* Fiber::Scheduler