Dear all, I want to redesign the bitset structure of combinatorial polyhedron and move it to `data_structures/bitset.pxi`. This includes some changes to bitset.pxi. Please comment, whether the proposed design changes on the ticket are ok. Mostly they are the following:
1. Define most of the functions in bitset.pxi for fuzed types. 2. Move functions that can be optimized by intrinsics to a seperate file. 3. (Not yet done, but also important.) Optimize some functions in bitset.pxi by intrinsics. This includes an overalignment condition. One disadvantage of overalignment is that it makes realloc much more complicated. Small bitsets also need more memory. 4. Indirect typecast of functions in `bitset.pxi` will no longer be possible. E.g. you cannot call `bitset_add` with signature `(bitset_t, PyObject)`, but `(bitset_t, int)` or `(bitset_t, size_t)` or similar are ok. See https://trac.sagemath.org/ticket/30572. Eventually, this should go into smaller tickets. But until then it would be good to know, if the general direction is acceptable or which part is not. See https://trac.sagemath.org/ticket/30549 for more detail. -- 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/06b59c3f-86be-4853-a91c-8a05f42163e5n%40googlegroups.com.
