DenisBiryukov91
DenisBiryukov91
@imstevenpmwork This was kind of finished for the main branch at the moment of last commit, but due to transition async-std->Tokyo, task termination part would likely need to be redone,...
Proper fix for memory leaks (#695 ) would likely also address this issue.
To allow providing options inline and specifying only non-default values we can probably try to use macros as proposed here https://stackoverflow.com/questions/13716913/default-value-for-struct-member-in-c.
The issue should no longer arise in dev/1.0.0 branch since the sizes and alignments of zenoh-rust types are no longer hardcoded, but fetched from rust compiler.
Already implemented in dev/1.0.0
for non-blocking channels it is necessary to call z_check on objects returned by try_recv()
@TheGoncaloSilva Could you try publishing smaller messages (i.e. up to 10 - 20 KB) and let us know if it works ? Could you also try publishing your bigger messages...
Given that connect/retry field is an Option (i.e. sort of a variant field / enum) - it seems natural and less error-prone to force user to set it as an...
~~Maybe instead of atexit, we could use a static variable that will call all drop logic in its destructor, at least this guaranteed by C++ standard to work correctly.~~ No...
There is also docs/examples.rst that needs to be updated