I think we should setup a uniform code format for Hyst. There is a super-easy way to automate this. We provide an .xml file describing the format which Eclipse's code formatter can parse (this can be version controlled in the repository). This can be exported from Eclipse's code formatter (I already have one I use myself to make code generation closer to what I expect).
I've done this type of setup recently for another C++ project I'm working on, and I've found it actually saves me time when coding, since I just save with ctrl+s instead of playing with formatting when I'm editing things.
I think we should setup a uniform code format for Hyst. There is a super-easy way to automate this. We provide an .xml file describing the format which Eclipse's code formatter can parse (this can be version controlled in the repository). This can be exported from Eclipse's code formatter (I already have one I use myself to make code generation closer to what I expect).
I've done this type of setup recently for another C++ project I'm working on, and I've found it actually saves me time when coding, since I just save with ctrl+s instead of playing with formatting when I'm editing things.
What do you think Talyor?