`webgraph analyze dissect`

[zommiommy]

We should update and introduce the dissect tool written by Davide:
https://github.com/colobrodo/webgraph-tools/blob/main/src/dissect/dec_stats_and_count.rs

Maybe it can be part of webgraph analyze codes as we alreay compute that information.

[vigna]

What does in addition?

[zommiommy]

Currently, we only print the size of each part using the top-k optimal codes, not the "current" codes

[colobrodo]

Hi, I just saw this issue.
I created that tool because I want to know the number of bits used by each component and also the number of integers written with the current code. I can't find that information using the "analyze codes" function if the code is not already the best one. Maybe there is already a way to do this, but I haven't found it.