Could you use RAII to call a lambda?
On 22 July 2014 20:31, Vladimir Pouzanov farcal...@gmail.com wrote:
One note on why there's no after_each:
You cannot really make sure that the epilogue is being called, so if you
need to do anything after your test case, use RAII in before_each.
On
It's great to see Hamcrest ported to Rust.
On 22 July 2014 20:06, Vladimir Pouzanov farcal...@gmail.com wrote:
I've just published a tiny test framework: shiny at
https://github.com/farcaller/shiny. It's best used with hamcrest-rust.
This library exists because I find it ugly to redefine
Hi. I want to use the existing I/O types (files, sockets, etc.) with
epoll. Is there an API call to get hold of their file descriptors?
--Nat
--
http://www.natpryce.com
___
Rust-dev mailing list
Rust-dev@mozilla.org
be interested in https://github.com/rust-lang/rust/pull/15643
which may add support for acquiring the file descriptor. That PR has
dome discussion about the hazards of doing so, as well.
On Sun, Jul 13, 2014 at 4:43 AM, Nat Pryce nat.pr...@gmail.com wrote:
Hi. I want to use the existing I/O types
form a lower layer
`libnative` API...
On 14 July 2014 22:26, Nat Pryce nat.pr...@gmail.com wrote:
Are there plans to better link the standard I/O APIs and the platform's
native I/O? For example, to control devices (on Linux often done by
ioctl,
which needs a file descriptor), use non-IP
://Zinc.rs)!
On 14 Jul 2014 23:15, Nat Pryce nat.pr...@gmail.com wrote:
I'm currently using the native API to implement new I/O abstractions for
GPIO, I2C, etc. But really want to combine them with the existing File and
socket APIs. I've had to copy code from the native runtime library to
convert
On Sunday, July 6, 2014, Tony Arcieri basc...@gmail.com wrote:
On Sat, Jul 5, 2014 at 8:07 AM, Nat Pryce nat.pr...@gmail.com
javascript:_e(%7B%7D,'cvml','nat.pr...@gmail.com'); wrote:
I've been trying to write tasks that wait for both I/O and channel
communication. I've been told
I've been trying to write tasks that wait for both I/O and channel
communication. I've been told that, to maximise communication performance,
channels do not support selecting of both channels and I/O objects.
Therefore a program should signal to a task that is waiting for I/O over
another I/O
