KEY_ALREADY_EXISTS in FixedOrderedMultiMap #194

Closed
opened 2020-09-08 16:16:19 +02:00 by taheran · 0 comments
Member

I just notice that there is a KEY_ALREADY_EXISTS in FixedOrderedMultiMap. It does not seem logical for a multimap, and it is not used in the implementation.

Also CLASS_IDs for FixedMap and FixedOrderedMultiMap are the same.

I just notice that there is a KEY_ALREADY_EXISTS in FixedOrderedMultiMap. It does not seem logical for a multimap, and it is not used in the implementation. Also CLASS_IDs for FixedMap and FixedOrderedMultiMap are the same.
taheran added the
question
label 2020-09-08 16:16:19 +02:00
gaisser added
bug
and removed
question
labels 2020-09-22 16:12:00 +02:00
muellerr referenced this issue from a commit 2020-09-29 14:59:55 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fsfw/fsfw#194
No description provided.