You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.Rmd
+6-3Lines changed: 6 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -259,9 +259,11 @@ close(s2)
259
259
260
260
{nanonext} implements a deferred evaluation pipe `%>>%` for working with potentially unresolved values.
261
261
262
-
Simply pipe the value forward into a function or series of functions and it either evaluates or returns an 'unresolvedExpr', where the result may be accessed at `$data`. This will also return an 'unresolvedExpr' recursively by design whilst unresolved. However `$data` resolves to the evaluated expression when the original value does.
262
+
Simply pipe the value forward into a function or series of functions and it either evaluates or returns an 'unresolvedExpr'.
263
263
264
-
It is possible to use `unresolved()` around the `$data` field to test for resolution, as in the example below.
264
+
The result may be queried at `$data`, which will return another 'unresolvedExpr' recursively (by design) whilst unresolved. However when the original value resolves, the 'unresolvedExpr' will resolve into a 'resolvedExpr' and the evaluated expression may then be accessed at \code{$data}.
265
+
266
+
It is possible to use `unresolved()` around a 'unresolvedExpr' or its `$data` field to test for resolution, as in the example below.
265
267
266
268
The pipe operator semantics are similar to R's base pipe `|>`:
267
269
@@ -283,7 +285,8 @@ unresolved(res$data)
283
285
284
286
# sending a message causes both 'msg' and 'res' to resolve
0 commit comments