On Fri, Dec 9, 2011 at 6:55 PM, Dave Herman <[email protected]> wrote:
> - In my experience, different styles between projects don't really > distract much. You get used to the style used there, and everyone's a > grown-up and understands they stick with the style of that group, even if > it's not their preferred style. > That's fine when you work mostly on one project that has a consistent style. If you switch between projects, then you have to remember which style to use for each project, probably even look it up for more obscure issues. The kicker is if you move code between projects; then you're stuck with style inconsistencies or else reformatting the moved code ... which inhibits future merging. - *Compilers* that are obnoxious about dotting every i and crossing every t > are a very different thing from *tools* that enforce style. Running a lint > tool, or tying a lint tool to a build process, or to a check-in process -- > those things all make perfect sense to me. But yelling at me for > indentation when I'm trying to hack? > Do you really write code using arbitrary indentation and other style, and then reformat it to the project style when you submit patches? I've never noticed anyone doing that. On the contrary, I think I'd crank code out faster if I didn't have to keep checking that I'm using the correct style for the project I'm working in. > I just don't see this experiment as worthwhile when we have so many > important problems to work on. > That makes sense. I'll try again next language :-). Rob -- "If we claim to be without sin, we deceive ourselves and the truth is not in us. If we confess our sins, he is faithful and just and will forgive us our sins and purify us from all unrighteousness. If we claim we have not sinned, we make him out to be a liar and his word is not in us." [1 John 1:8-10]
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
