We waited a long time here, but there has been no objections. I just went ahead and created the module: < https://wiki.mozilla.org/Modules/Core#C.2B.2B.2FRust_usage.2C_tools.2C_and_style>. I decided to own this since nobody else was in a rush to do so, but the decision making in the various sub-parts of this module is owned by the respective peers who are expert in that area.
Cheers, Ehsan On Wed, Apr 27, 2016 at 3:12 AM, Ehsan Akhgari <[email protected]> wrote: > On 2016-04-27 3:29 AM, Nathan Froyd wrote: > > On Tue, Apr 26, 2016 at 10:40 AM, Henri Sivonen <[email protected]> > wrote: > >> On Wed, Mar 9, 2016 at 11:20 PM, Nathan Froyd <[email protected]> > wrote: > >>> - formatting/naming style (The C++ bits of > >>> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_ > guide/Coding_Style > >>> , essentially) > >> ... > >>> The Rust community also > >>> has somewhat more established guidelines around style as well. > >> > >> Can we, please, please decide not to fight the Rust team's and Rust > >> community's style choices and write Rust code in Gecko to look like > >> normal Rust code even if this makes Rust code in Gecko differ from C++ > >> code in Gecko? That is, no aFoo or mFoo but unprefixed_snake_case and > >> formatting code in general like rustfmt does it by default. > > > > I could have been clearer in my original email. My plan was to take > > whatever conventions Rust has around style, including whatever rustfmt > > does by default, and let that be our Rust style. I'm happy to let > > style wars be a settled thing as far as Rust goes. > > Seconded. Our rust style should be "whatever rustfmt does by default." > No need to have another battle ground for the holy style wars, we have > enough of those as it is! :-) > > If and when that proves to be insufficient, we can re-evaluate. > -- Ehsan _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
