raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

clean GraphAssembly in scaladoc since which has gone for a while (#579)

Browse source
This commit is contained in:
Dongxu Wang 2023-08-18 07:07:52 +08:00 • committed by GitHub
parent 3775a18c2e
commit 580f12c29f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
stream/src/main/scala/org/apache/pekko/stream/impl/TraversalBuilder.scala
View file

@ -38,8 +38,7 @@ import pekko.util.unused
* number (and those which are not receive different numbers). This feature can be used to
* - materialize a graph, using the slots as indices to an array of Publishers/Subscribers that need to be wired
* together
* - fuse a graph, using the slots to construct a [[pekko.stream.impl.fusing.GraphInterpreter.GraphAssembly]] which
* uses a similar layout
* - fuse a graph
* - create a DOT formatted output for visualization
* - convert the graph to another data structure
*

5
stream/src/main/scala/org/apache/pekko/stream/impl/fusing/GraphInterpreter.scala
View file

@ -140,8 +140,9 @@ import pekko.stream.stage._
/**
* INTERNAL API
*
* From an external viewpoint, the GraphInterpreter takes an assembly of graph processing stages encoded as a
* [[GraphInterpreter#GraphAssembly]] object and provides facilities to execute and interact with this assembly.
* From an external viewpoint, the GraphInterpreter takes an assembly of graph processing stages and provides facilities
* to execute and interact with this assembly.
*
* The lifecycle of the Interpreter is roughly the following:
* - [[init]] is called
* - [[execute]] is called whenever there is need for execution, providing an upper limit on the processed events