Personally, I dislike the passive voice, and I do what I can to eliminate it in my writing. To my mind, though, we should make only the smallest possible edits to transform passive into active voice. Anything more runs the risk of changing the meaning.
With the Agent example Hassan provided: The `Agent` module provides a basic server implementation that allows state to be retrieved and updated via a simple API. I would simply make the subject of the dependent clause explicit, like this: The `Agent` module provides a basic server implementation that allows us to retrieve and update state via a simple API. The result is shorter and more direct, and the meaning is exactly the same. On Sat, Aug 3, 2019 at 1:42 PM damien krotkine <[email protected]> wrote: > Hi, > > I’m respectfully not convinced by your example. The first change seems > wrong to me: processes don’t *need* to store state. They don’t have any > needs, wills, regrets or feelings. It’s the developer that has a need to > store state. The change seems inappropriate. > > The second diff actually changes the meaning of the sentence IMO. It looks > like it provides two things: an implementation and an API, as if the API > wasn’t part of the implementation. > > I’m not convinced, it would make the docs less precise and harder to > understand. My 2 cents of course :) > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/53ebe2d5-0cd2-4a31-88f6-e0aaf2851dfc%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAEBdXeDED%3DvN6Xv4%3DsegoV5nSrV5pd3nB4X3tGL2wje_qNf9OA%40mail.gmail.com.
