Pauli
Pauli
The insurmountable contention here is over making the list's internal structures open so that code can directly access the fields versus having wrapper functions that keeps them opaque. The structures...
> I do not see us ever replacing the internal list implementation. The debug version I've added does exactly this???
The implementation of threading isn't critical -- it's an implementation detail. Locks is one option. Lock free lists can also be done (lock free data structures are pretty interesting but...
What are the compelling arguments in favour of the new suggestion? The accessor functions are the _incumbent_, changes from that generally require a compelling reason. So far the reasons seem...
OTC: **which path should be chosen?**
and squashed down....
I've dropped the hold. Even if approved I won't merge until there is a chance to add it anew.
@levitte, my understanding was that @hlandau was going to revisit all of the seperate implementations and change them to use list.h in due course. The _debacle_ is the point of...
Oops. I switched the memsets to call the new init_elem function instead.
ping for second review