Hope

This is what I get so far (), I think it is well enough for me, and do not have many overlaps with the current excellent `fst`.

I knew this day would come, but not realized it would come so quickly. These is such an issue: I could never read the whole chunk of data into the...

Nice! I think I can make the function `filter_fst` right away. This should be useful even currently it might not be fast enough.

The work is almost done, though not published on CRAN yet. See .

CRAN already, FYI:

Is there a way for me to get the path from a fst_table?

This is great! I could try build more facilities on it if possible.

I am not so familiar with the implementations underneath, what you mention as "low-level abilities" are acutually quite "high-level" to me. If these abilities could be done in `fst`, faster...

I've designed a new tool to work with fst, which is considered to be more memory efficient. Link:

I've introduce `fst` package to more users and they encouter this as well. Is there any progress to solve it? Thanks.