Skip to content

Commit

Permalink
Fix typo
Browse files Browse the repository at this point in the history
'nonmonotonicity' -> 'non-monotonicity'
  • Loading branch information
stevemns committed Oct 11, 2017
1 parent 0d11e61 commit d4a50e2
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion input/5_eventual.md
Original file line number Diff line number Diff line change
Expand Up @@ -436,7 +436,7 @@ What does this mean in practice? First, monotonic logic can reach definite concl

So why are two operations that are on the surface equivalent different? Why is adding two numbers monotonic, but calculating an aggregation over two nodes not? Because the aggregation does not only calculate a sum but also asserts that it has seen all of the values. And the only way to guarantee that is to coordinate across nodes and ensure that the node performing the calculation has really seen all of the values within the system.

Thus, in order to handle nonmonotonicity one needs to either use distributed coordination to ensure that assertions are made only after all the information is known or make assertions with the caveat that the conclusion can be invalidated later on.
Thus, in order to handle non-monotonicity one needs to either use distributed coordination to ensure that assertions are made only after all the information is known or make assertions with the caveat that the conclusion can be invalidated later on.

Handling non-monotonicity is important for reasons of expressiveness. This comes down to being able to express non-monotone things; for example, it is nice to be able to say that the total of some column is X. The system must detect that this kind of computation requires a global coordination boundary to ensure that we have seen all the entities.

Expand Down

0 comments on commit d4a50e2

Please sign in to comment.