mirrors/salsa
1
0
Fork 0
mirror of https://github.com/salsa-rs/salsa.git synced 2025-01-28 23:32:56 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix doc typos

Browse source
This commit is contained in:
Geoff Shannon 2020-05-16 13:39:11 -07:00
parent 38e708b68b
commit 294b12f719
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
book/src/common_patterns/on_demand_inputs.md
View file

@ -12,7 +12,7 @@ That is, when someone requests the text of a file for the first time:
3. Invalidate the cached file once the watcher sends a change notification. 3. Invalidate the cached file once the watcher sends a change notification.
This is possible to achieve in salsa, using a derived query and `report_synthetic_read` and `invalidate` queries. This is possible to achieve in salsa, using a derived query and `report_synthetic_read` and `invalidate` queries.
The setup looks roughtly like this: The setup looks roughly like this:
```rust,ignore ```rust,ignore
#[salsa::query_group(VfsDatabaseStorage)] #[salsa::query_group(VfsDatabaseStorage)]

4
book/src/common_patterns/selection.md
View file

@ -62,8 +62,8 @@ This will result in a dependency graph like so:
request_text --> parse --> header --> content_type --> (other queries) request_text --> parse --> header --> content_type --> (other queries)
``` ```
The advantage of this is that changes that only effect the "body" of The advantage of this is that changes that only effect the "body" or
only consume small parts of itthe request will only consume small parts of the request will
not require us to re-execute `content_type` at all. This would be particularly not require us to re-execute `content_type` at all. This would be particularly
valuable if there are a lot of dependent headers. valuable if there are a lot of dependent headers.