Jason Fan

Not sure how helpful this would be, but one workaround would be to do something like: https://gist.github.com/theJasonFan/65fa3e514a7fe7b179412f41f7c7168b And invoke `bench_function(...)` in a binary. It's quite hacky though. Note that criterion...

Thank you for the quick response. A couple thoughts: > Can Serde support be added without too much maintenance burden? AFAIK, serde compatibility can be added to `RawVector`, `BitVector`, and...

Ah yes, that would be quite non-trivial --- I understand your concern now. One possible, but inelegant, solution, would be to implement "stable" structs that mirror "in-memory" structs that could...

I ran into this issue as well. The intended behavior should be for ``` params { fooBar = false } ``` and ``` params.fooBar ``` to *both* create a `foo-bar`...

@pditommaso @marcodelapierre would you be willing mark this issue as a bug? This issue might cause unexpected reproducibility issues. Thanks!

@rob-p can chime in. I wonder if the solution right now is to provide some examples of how the kmer library can be used. We've written `kmer` iterators and canonical...

Hmm, @stela2502 what is the specific use case and type conversion(s) you would like? Regarding speed / usage: if you only need kmers of length

Would calling `bitmer_to_bytes()` then `[std::str::from_utf8](https://doc.rust-lang.org/std/str/fn.from_utf8.html)` work for your use case? We do something like this in the tests where we compare kmer representations to a sequence of bytes: https://github.com/COMBINE-lab/kmers/blob/15016e2d7fdc8be34d57ba77b269c74cd81f8901/src/kmer.rs#L195

> That's not a use case we have, so I cannot justify putting quite a lot of time in it. Most of the time will be getting into the details...