Programming Ruby 3.2 (5th Edition): B1.0 page 203, sentences difficult to understand

page 203, first paragraph, line 2-3 :
ractor. The entrance lines are infinite, and the sending call is guaranteed not to block
for “if this goes wrong you have much larger problems” meanings of “guaranteed.”
I have read again and again and don’t really understood. For what I have experimented until now, I would be satisfied with :
The entrance lines are infinite, and the sending call is guaranteed not to block.
+++++ paragraph 5, last line :
… … … … … … … … … … … … … … … … … … The only
way to get a value into a ractor is via send.
I can imagine “get” as obtaining that a new value is introduced into the ractor, but combined with the following “into” and “send”, I would feel more natural to say set :
The only way to set a value into a ractor is via send.
+++++ paragraph 7, second bullet :
The code block hits a Ractor.recieve call, in which case it waits for a call to send, the
Not clear at first glance. I would say :
in which case it waits for another ractor calling send with this [known] ractor as a receiver, …
known is not indispensable, just to echo the first line of this page.
Popular Prag Prog topics










Other popular topics










Latest in PragProg
Latest (all)
Categories:
Popular Portals
- /elixir
- /opensuse
- /rust
- /kotlin
- /ruby
- /erlang
- /python
- /clojure
- /react
- /quarkus
- /go
- /vapor
- /v
- /react-native
- /wasm
- /security
- /django
- /nodejs
- /centos
- /haskell
- /rails
- /fable
- /gleam
- /swift
- /js
- /deno
- /assemblyscript
- /tailwind
- /laravel
- /symfony
- /phoenix
- /crystal
- /typescript
- /debian
- /adonisjs
- /julia
- /arch-linux
- /svelte
- /spring
- /flutter
- /c-plus-plus
- /preact
- /actix
- /java
- /angular
- /ocaml
- /zig
- /kubuntu
- /scala
- /zotonic
- /vim
- /rocky
- /lisp
- /html
- /keyboards
- /nim
- /vuejs
- /emacs
- /elm
- /nerves