revert pipes, push to later release

Author: shikokuchuo

DESCRIPTION

@@ -1,7 +1,7 @@
 Package: nanonext
 Type: Package
 Title: NNG (Nanomsg Next Gen) Lightweight Messaging Library
-Version: 0.2.0.9007
+Version: 0.2.0.9008
 Description: R binding for NNG (Nanomsg Next Gen), a successor to ZeroMQ. NNG is 
     a socket library providing high-performance scalability protocols,
     implementing a cross-platform standard for messaging and communications.

NAMESPACE

@@ -17,18 +17,14 @@ S3method(print,nanoListener)
 S3method(print,nanoObject)
 S3method(print,nanoSocket)
 S3method(print,recvAio)
-S3method(print,resolvedExpr)
 S3method(print,sendAio)
-S3method(print,unresolvedExpr)
 S3method(print,unresolvedValue)
 S3method(setopt,nanoContext)
 S3method(setopt,nanoDialer)
 S3method(setopt,nanoListener)
 S3method(setopt,nanoSocket)
 S3method(start,nanoDialer)
 S3method(start,nanoListener)
-export("%>>%")
-export("%~%")
 export(.mirai_scm)
 export(call_aio)
 export(context)

NEWS.md

@@ -1,10 +1,9 @@
-# nanonext 0.2.0.9007 (development)
+# nanonext 0.2.0.9008 (development)
 
 #### New Features
 
 * Aio values `$result`, `$data` and `$raw` now resolve automatically without requiring `call_aio()`. Access the values directly and an 'unresolved' logical NA will be returned if the Aio operation is yet to complete.
 * `unresolved()` added as an auxiliary function to query whether an Aio is unresolved, for use in control flow statements.
-* Implements the Deferred Evaluation Pipe `%>>%` and Meanwhile / Concurrency Pipe `%~%` for working with potentially unresolved values.
 * Integer error values generated by receive functions are now classed 'errorValue'. `is_error_value()` helper function included.
 * `is_nul_byte()` added as a helper function for request/reply setups.
 * `survey_time()` added as a convenience function for surveyor/respondent patterns.

R/pipe.R

@@ -47,14 +47,12 @@ Implemented transports:
 2. [Interfaces](#interfaces)
 3. [Cross-language Exchange](#cross-language-exchange)
 4. [Async and Concurrency](#async-and-concurrency)
-5. [Deferred Evaluation Pipe](#deferred-evaluation-pipe)
-6. [Meanwhile (Concurrency) Pipe](#meanwhile-concurrency-pipe)
-7. [RPC and Distributed Computing](#rpc-and-distributed-computing)
-8. [Publisher / Subscriber Model](#publisher-subscriber-model)
-9. [Surveyor / Repondent Model](#surveyor-respondent-model)
-10. [ncurl Minimalist http Client](#ncurl-minimalist-http-client)
-11. [Building from source](#building-from-source)
-12. [Links](#links)
+5. [RPC and Distributed Computing](#rpc-and-distributed-computing)
+6. [Publisher / Subscriber Model](#publisher-subscriber-model)
+7. [Surveyor / Repondent Model](#surveyor-respondent-model)
+8. [ncurl Minimalist http Client](#ncurl-minimalist-http-client)
+9. [Building from source](#building-from-source)
+10. [Links](#links)
 
 ### Installation
 
@@ -256,84 +254,6 @@ close(s2)
 
 [« Back to ToC](#table-of-contents)
 
-### Deferred Evaluation Pipe
-
-{nanonext} implements a deferred evaluation pipe `%>>%` for working with potentially unresolved values.
-
-Simply pipe the value forward into a function or series of functions and it either evaluates or returns an 'unresolvedExpr'.
-
-The result may be queried at `$data`, which will return another 'unresolvedExpr' whilst unresolved. However when the original value resolves, the 'unresolvedExpr' will simultaneously resolve into a 'resolvedExpr', for which the evaluated result will be available at `$data`. 
-
-It is possible to use `unresolved()` around a 'unresolvedExpr' or its `$data` element to test for resolution, as in the example below.
-
-The pipe operator semantics are similar to R's base pipe `|>`:
-
-`x %>>% f` is equivalent to `f(x)` <br />
-`x %>>% f()` is equivalent to `f(x)` <br />
-`x %>>% f(y)` is equivalent to `f(x, y)`
-
-```{r pipe1}
-
-s1 <- socket("pair", listen = "inproc://dep")
-s2 <- socket("pair", dial = "inproc://dep")
-
-# request an aysnc receive with no messages waiting
-msg <- recv_aio(s2)
-
-res <- msg$data %>>% c(2, 3) %>>% as.character()
-res
-unresolved(res$data)
-
-# sending a message causes both 'msg' and 'res' to resolve
-s <- send_aio(s1, 1)
-unresolved(res)
-res
-res$data
-
-close(s1)
-close(s2)
-
-```
-
-[&laquo; Back to ToC](#table-of-contents)
-
-### Meanwhile (Concurrency) Pipe
-
-The deferred evaluation pipe sequence may be terminated with a meanwhile (or concurrency) pipe `%~%` which:
-
-(i) provides certainty of the return value, which will always be the evaluated result rather than a 'resolvedExpr'
-
-(ii) makes it convenient to write concurrent code which runs whilst the expression is resolving
-
-`x %~% expr`
-
-is equivalent to the following expression, finally returning x:
-
-`if (unresolved(x)) while (unresolved(x <- x$data)) {expr}; x`
-
-Use it in the following way:
-
-```{r pipe2}
-
-s1 <- socket("pair", listen = "inproc://meanwhile")
-s2 <- socket("pair", dial = "inproc://meanwhile")
-
-n <- 1L
-rec <- recv_aio(s2)
-a <- rec$data %>>% identical(data.frame()) %~% {
-  if (n == 5) send_aio(s1, data.frame())
-  cat("unresolved", n, "\n")
-  n <- n + 1
-}
-a
-
-close(s1)
-close(s2)
-
-```
-
-[&laquo; Back to ToC](#table-of-contents)
-
 ### RPC and Distributed Computing
 
 {nanonext} implements remote procedure calls (RPC) using NNG's req/rep protocol to provide a basis for distributed computing.