Come on, even that flag's name is ridiculous. They basically say, for example, that writing camel case, which is the preferred style in most of the projects I've seen, is bad style. Do they like being unnecessarily antipathetic? People think about their personal preferred style for years, and they have very good reasons for choosing them. And in _many_ cases, it's exactly the style that's called bad by Rust's creators.
How about making it the opposite, '#![allow(default_style)]'? Or at least '#![allow(non_default_style)]'?
In some cases skirting style can be harmful (e.g. in match statements there's an ambiguity with enum variants and variable bindings that is not an issue because of the style lints).
But I get your point. I think people would be open to that naming change if you file an issue.
How about making it the opposite, '#![allow(default_style)]'? Or at least '#![allow(non_default_style)]'?