Tom Kaitchuck
Tom Kaitchuck
This fixes #225 It uses the key type as the type specialization even when lookup occurs with a different type.
There are hardware instructions on X86 for approximate inverse square root and square root which can improved upon via newton's method. See the for loop at the bottom of `bodies_advance`...
**Problem description** There was some confusion in https://github.com/pravega/pravega-client-rust/issues/438 caused by the default parameter resulting in poor throughput. **Problem location** https://github.com/pravega/pravega-client-rust/blob/73b46a66b2fd32325c5acd0ab619d40483a14a7f/python/src/stream_manager.rs#L407 **Suggestions for an improvement** Make this more explicit in the...
FAIL tests/client.test.ts ● Basic test on manager, reader, and writer › main assert.strictEqual(received, expected) Expected value to strictly be equal to: 6 Received: 4 Message: expected 4 to equal 6...
It would be good if we could identify a log line when it is ready and wait for that to be logged. _Originally posted by @tkaitchuck in https://github.com/pravega/pravega-client-rust/pull/190#discussion_r541478797_
**Problem description** Currently there is a timeout internal to `get_segment_slice_async` this causes problems with some of the integration tests. For example: https://github.com/pravega/pravega-client-rust/runs/7682183505?check_suite_focus=true **Problem location** Reader.aquire_segmnet **Suggestions for an improvement** Remove...
**Problem description** See discussion here: https://github.com/pravega/pravega-client-rust/pull/358/files#r841049765
**Problem description** Currently the Rust API supports async writes. However calls from Python a made synchronously. We should expose a way to write events and receive a python future. **Problem...
**Problem description** We should use https://docs.rs/futures/0.3.14/futures/channel/index.html for the channels in our public APIs so that users are not dependent on Tokio. **Problem location** EventStreamWriter (probably others) **Suggestions for an improvement**...
**Problem description** We forked bincode2 from bincode when bincode was maintained. However people from the servo team stepped up and started maintaining bincode. As a result bincode caught up with...