Attention is currently required from: pespin. fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/27720 )

Change subject: scheduler: remove redundant OSMO_ASSERT() statements ......................................................................

Patch Set 1: Code-Review+2

(1 comment)

Patchset:

PS1:

That's precisely the point of the asserts, to describe and check that "guaranteed" situation, so tha […]

Yes, I agree with the concept in general. But on the other hand we should not put assert()s everywhere to address every possible failure vector. In this context it's hard to imagine why would somebody change bts_model_l1sap_down() to call this function on receipt of a different prim type, given that it's clear from the function name what kind of the input it expects...