lostluck commented on a change in pull request #15057:
URL: https://github.com/apache/beam/pull/15057#discussion_r659043365
##########
File path: website/www/site/content/en/documentation/programming-guide.md
##########
@@ -522,6 +572,12 @@ together transforms to create a pipeline that successively
modifies input data:
| [Third Transform])
{{< /highlight >}}
+{{< highlight go >}}
+[Second PCollection] := beam.ParDo(s, [First Transform], [Initial Input
PCollection])
+[Third PCollection] := beam.ParDo(s, [Second Transform], [Second PCollection])
Review comment:
This one is reasonable since it's abstract code anyway. However, I'd
rather not force a generation of Go SDK users to repeatedly use `scope` for a
pervasive variable. Eventually too much such repetition is not useful and draws
focus from the distinct parts of the call.
I agree that towards the pipeline phase, we should explain the scope
variable better, what it's for (referring to the section on composites), and
that conventionally, it's abbreviated to 's' which is like how
`context.Context` is abbreviated to `ctx`, and `io.Reader` and `io.Writer`
become `r` and `w` respectively.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
