@@ -106,7 +106,7 @@ Let's run it and wait for the fetch to complete:
106
106
107
107
``` scala
108
108
fetchOne.runA[Id ]
109
- // [2347 ] One ToString 1
109
+ // [2384 ] One ToString 1
110
110
// res3: cats.Id[String] = 1
111
111
```
112
112
@@ -124,7 +124,7 @@ When executing the above fetch, note how the three identities get batched and th
124
124
125
125
``` scala
126
126
fetchThree.runA[Id ]
127
- // [2347 ] Many ToString NonEmptyList(3, 1, 2)
127
+ // [2384 ] Many ToString NonEmptyList(3, 1, 2)
128
128
// res5: cats.Id[(String, String, String)] = (1,2,3)
129
129
```
130
130
@@ -165,8 +165,8 @@ Note how the two independent data fetches run in parallel, minimizing the latenc
165
165
166
166
``` scala
167
167
fetchMulti.runA[Id ]
168
- // [2348 ] One Length one
169
- // [2347 ] One ToString 1
168
+ // [2385 ] One Length one
169
+ // [2384 ] One ToString 1
170
170
// res7: cats.Id[(String, Int)] = (1,3)
171
171
```
172
172
@@ -185,7 +185,7 @@ While running it, notice that the data source is only queried once. The next tim
185
185
186
186
``` scala
187
187
fetchTwice.runA[Id ]
188
- // [2347 ] One ToString 1
188
+ // [2384 ] One ToString 1
189
189
// res8: cats.Id[(String, String)] = (1,1)
190
190
```
191
191
## Fetch in the wild
0 commit comments