Is “const correctness” tedious?
Type safety requires you to annotate your code with type information. In theory, expressing this type information isn’t necessary — witness untyped languages as an example of this. However in practice, programmers often know in their heads a lot of interesting information about their code, so type safety (and, by extension, const correctness) merely provide structured ways to get this information into their keyboards. Short answer: yes, const correctness is tedious.