what pros & cons there saving formula some-more granularly during record level?

what cruise kind code-to-files-mapping?

~/proj/myclass.ext  
~/proj/myclass:constructors.ext  
~/proj/myclass:properties.ext  
~/proj/myclass:method-one.ext  
~/proj/myclass:method-two:int.ext
~/proj/myclass:method-two:string.ext

in libel some-more functional-oriented:

~/proj/definitions.ext  
~/proj/function-one.ext  
~/proj/function-two:int.ext  
~/proj/function-two:string.ext  
...

the indicate operative the project, don't see multiplicity files.

we competence presumably have kind daemon slight keeps reflection myclass.ext record ideally sync garland files, the favorite formula editor sees nonetheless shows judicious aggregation, kind reworking wholly happens set pre+post-commit hooks.

now, given wouldn't prying idea's doing it's good idea, let's worry ourselves the doing sum (the how); let's suspect we've got ideal doing thought work well us.

what i us together good list pros & cons approach, both during high turn during some-more specific low levels your concern.

when we'll finished brainstorming observant any answer's votes, should simply good thought not. therefore, greatfully pro/con per answer.

edit

from answers generally scott's, i subsequent the wholly genuine proceed thought competence useful, means move involuntary register altered class:method couples footnote biased any commit-to-vcs message. many some-more simply achieved little scripts run before commits, transform summary template accordingly.