Update some QLDoc comments

This commit is contained in:
Asger F
2022-09-08 09:17:49 +02:00
parent 576e320bf5
commit 7737e75427
3 changed files with 7 additions and 7 deletions

View File

@@ -185,7 +185,7 @@ module StepSummary {
}
/**
* Holds if `nodeFrom` is being written to the `content` content of the object in `nodeTo`.
* Holds if `nodeFrom` is being written to the `contents` of the object in `nodeTo`.
*
* Note that `nodeTo` will always be a local source node that flows to the place where the content
* is written in `basicStoreStep`. This may lead to the flow of information going "back in time"
@@ -204,7 +204,7 @@ module StepSummary {
* def bar(x):
* z = x.attr
* ```
* for the attribute write `x.attr = y`, we will have `content` being the literal string `"attr"`,
* for the attribute write `x.attr = y`, we will have `contents` being the literal string `"attr"`,
* `nodeFrom` will be `y`, and `nodeTo` will be the object `Foo()` created on the first line of the
* function. This means we will track the fact that `x.attr` can have the type of `y` into the
* assignment to `z` inside `bar`, even though this attribute write happens _after_ `bar` is called.

View File

@@ -122,11 +122,11 @@ predicate returnStep(Node nodeFrom, Node nodeTo) {
}
/**
* Holds if `nodeFrom` is being written to the `content` content of the object
* Holds if `nodeFrom` is being written to the `contents` of the object
* in `nodeTo`.
*
* Note that the choice of `nodeTo` does not have to make sense
* "chronologically". All we care about is whether the `content` content of
* "chronologically". All we care about is whether the `contents` of
* `nodeTo` can have a specific type, and the assumption is that if a specific
* type appears here, then any access of that particular content can yield
* something of that particular type.
@@ -145,7 +145,7 @@ predicate returnStep(Node nodeFrom, Node nodeTo) {
* z = x.content
* end
* ```
* for the content write `x.content = y`, we will have `content` being the
* for the content write `x.content = y`, we will have `contents` being the
* literal string `"content"`, `nodeFrom` will be `y`, and `nodeTo` will be the
* `Foo` object created on the first line of the function. This means we will
* track the fact that `x.content` can have the type of `y` into the assignment