@bjorn I'll be honest, I'm still not convinced, even if I won't go against the 
move for such a detail.

To me, It's not the fact that a header is light or not that matters, it's the 
fact that classes or methods are documented at one place with no other
information in the way. 

If I have to scroll through out the source file to find some documentation, 
along with how it is implemented, then I think I've lost the benefit of 
searching only for documentation.

Your way of doing is making sense only when you consider your API 100% 
self-explanatory and you want the programmer to look at the 
implementation at the same time he/she's looking at the doc.

So, nope, I'm not convinced, but I won't get angry for it, don't worry. ;)
I was rather curious in fact. (You never know when you can learn something 
useful) :)

Best regards,

@Bertram25[1] The problem with writing docs in the header is that the 
header is no longer a light file at all. In over 90% of the cases our 
documentation is superfluous and leaving it out in the header file makes 
sure the API of most classes will fit on one page. In the same spirit we no 
longer write inline functions in the class definition. 
For an example see 
https://github.com/mana/manaserv/blob/master/src/game-server/entity.h#L44[2] 
—Reply to this email directly or view it on GitHub[3].[4]



--------
[1] https://github.com/Bertram25
[2] https://github.com/mana/manaserv/blob/master/src/game-server/entity.h#L44
[3] https://github.com/mana/manaserv/pull/59/files#r4003922
[4] 
https://github.com/notifications/beacon/WqKnsNd1YYCmbBqMWnTBxenyG_tx
xjsvWD8k-Z_2K9FNLgUf-sq34rrtz0GyOwxN.gif