Thanks for this! Can you also add a test case to Documentation.test.cpp?

Whoops, wrong button

I'm not sure if this is the best way to add a test like this, because I feel like this is a much more complicated and nuanced test. Probably what would need to happen is every use of multiline comments (or vice versa) in Documentation.test.cpp should be replaced with a use of both (?) and check if their results are equal, but that just seems terrible to implement, and I'm not going to change the entire codebase for just that. 😓

Ideally, the end goal should probably always be congruence between multiline and single-line doc comments, such that someone could replace the --- with tabs, and add the --[=[ prefix and ]=] suffix and be left with the same rendered result no matter what. I'm just not sure how you would test such a thing without just testing both multiline and single-line doc comments for every test case.