We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is an issue to suggest that types follow Rust naming conventions.
Structs, enums, and traits follow CamelCase. Constants follow SCREAMING_SNAKE_CASE.
This affects a lot of types prefixed with Detail_.
Detail_
Examples: Detail_WaveCorrectKind -> DetailWaveCorrectKind Stitcher_Mode -> StitcherMode Detail_Blender_Feather -> DETAIL_BLENDER_FEATHER
Detail_WaveCorrectKind
DetailWaveCorrectKind
Stitcher_Mode
StitcherMode
Detail_Blender_Feather
DETAIL_BLENDER_FEATHER
This also affect enum variants.
A balance will have to be struct (: when dealing with things like the SphericalWarperTraitConst trait.
SphericalWarperTraitConst
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is an issue to suggest that types follow Rust naming conventions.
Structs, enums, and traits follow CamelCase.
Constants follow SCREAMING_SNAKE_CASE.
This affects a lot of types prefixed with
Detail_
.Examples:
Detail_WaveCorrectKind
->DetailWaveCorrectKind
Stitcher_Mode
->StitcherMode
Detail_Blender_Feather
->DETAIL_BLENDER_FEATHER
This also affect enum variants.
A balance will have to be struct (: when dealing with things like the
SphericalWarperTraitConst
trait.The text was updated successfully, but these errors were encountered: