Most of the bitsets used in the graph backend are to record sets of seen or active vertices. These sets are not sparse. But I think we have several places in the graph module where we use sets instead of bitsets for small number of vertices. Sparse bitsets could be useful in this case if effectively faster.
Le mercredi 23 septembre 2020 à 08:46:33 UTC+2, jonatha...@googlemail.com a écrit : > Thanks. I still can only guess, if people care about large bitsets like > this. > > I can try to make it available with the same syntax and then however likes > it, can just use it. > > Sébastien Labbé schrieb am Dienstag, 22. September 2020 um 16:07:15 UTC+2: > >> Am I the only one using larger bitsets? >>> >> >> Doing the following from SAGE_ROOT: >> >> git grep --name-only bitset >> >> shows that modules in sage using bitset are mostly graphs but also >> matroid, groups, combinat, data_structures, but also crypto, coding, misc >> and quivers. I don't know if those usage are for larger bitsets or not. >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2637cc6c-e6ff-4f3f-b24a-3c0294436a0fn%40googlegroups.com.
