Consider renaming NonFifoQueues about userver HOT 4 CLOSED

Hi! IMO, it's acceptable to leave NonFifo Queue name as-is. It follows from their name that they generally aim for queue (FIFO) semantics, but sometimes shuffle the elements in a difficult-to-predict order.

It may still worth it to document, in which situations FIFO order can be violated, namely that items from different producers may be consumed in unspecified order, but items from the same producer are always consumed in the order of Push.

NonFifo suffixes have just been dropped where possible, see this commit.

Could you please split the optimized SPSC queue into a separate issue?

from userver.

Hm, i'm pretty sure that it was still NonFifoSpscQueue when i created the issue, however your commit seems to be pushed 10 hours earlier – is that an artifact of the internal->external github synchronization you guys maintain?

Thinking more about NonFifo part - i see your point and maybe it's indeed better to just clean up a confusion in documentation, leaving name as is.

I'll file a separate issue for optimized Spsc version (edit: #71)

from userver.

is that an artifact of the internal->external github synchronization you guys maintain?

Yes, some work is still needed to complete the migration from the internal repo.

from userver.

Gkia.785

from userver.