Are Tasks one-to-one with the SchedulingClasses?

Are Tasks one-to-one with the SchedulingClasses?
My understanding is that the function descriptor of a task is globally unique, so the encapsulated into SchedulingClassDescriptor as well as the corresponding SchedulingClass is globally unique. But why does a SchedulingClass in the absl::flat_hash_map corresponds to a dual-ended queue (std::deque) when scheduling tasks?

I have figured it out and verified my idea through code testing.

1 Like