pointer bugs 2 about kanal HOT 6 CLOSED

Thanks for the report! I really appreciate your contributions to Kanal with reporting these bugs.
I don't think that's because of clone_sync.
I'm going to investigate this report and will let you know what was the problem.
Miri reports :

    |
224 |         self.ptr.as_ptr()
    |         ^^^^^^^^ using uninitialized data, but this operation requires initialized memory
    |

from kanal.

you might as well write tests for .clone_async() to make sure it does not have the same bug.

from kanal.

Nice catch, there was a race condition in the read future, that actually lead to finding another race condition in send future too!
Both are patched with f615c8c .
Could you please run your test with the following and check if the problem is solved?

[dependencies]
kanal = {git="https://github.com/fereidani/kanal"}
tokio = { version = "1", features = ["full"] }
anyhow = "*"

from kanal.

Nice! It works, closing, please do a release.

from kanal.

Sure, will do that tomorrow, I need to rerun benchmarks and additional tests.
If it's possible for you for the next reports please use Tokio like this:

fn main() {
    let rt = tokio::runtime::Builder::new_current_thread()
        .enable_time()
        .build()
        .unwrap();
    rt.block_on(async_fn()).unwrap();
}

because it is easier to debug this one using Miri and other debug tools.

from kanal.

No problem

from kanal.