Jay
As far as I know, no one is working on it.
I don't think it's a good idea to introduce avoidable clone behind a library interface. Current way allow callers to decide whether to create or reuse an owned string.
Perhaps this should be send to jemalloc/jemalloc as well. Without change from upstream or without updating musl versions bundled by rust, we may not be able to make it work.
> do you mean rust has its own bundled musl? Yes. > So it doesn't work if we just upgrade our own musl? No, it won't work. Though I'm not...
Thanks for the workaround. I think it's the same as setting the environment when invoking build like `env je_cv_pthread_getname_np=no cargo build`. If it's really caused by some outdated bundled library,...
Can you build [jemalloc](https://github.com/jemalloc/jemalloc) itself on illumos?
It's better to add it in the default feature list in this PR. This is still a breaking change for those rely on stats features without enabling it explicitly though.
What's the relations between tikv/agatedb and rocksdb-rs? Can you describe more on the motivation of building a new rocksdb implementation instead of agatedb?
> agatedb does not support snapshot isolation. agatedb is supposed to inherit all features badger supports, so it may support it at the moment, but it's supposed to support it...