I remember a time when the sole point of code review was to answer the question 'is this change going to break any other work currently in-progress?' That was it.

it was expected to be a short-duration fixed-scope activity with a clear Go-NoGo answer, and you would have gotten roasted for digressing into navel-gazing and distracted conversations about armchair philosophy. if the change worked as-advertised and didn't break your work, then it was a 'go', get back to work...