-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
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
Inconsistent use of whitespace #240
Comments
There doesn't appear to be a general style guide for JuliaOpt, but JuMP has its own, which says 4 spaces. It's pretty much the de facto standard anyway. |
ararslan
added a commit
that referenced
this issue
Nov 7, 2018
The package currently uses a mixture of indentation, including 2- and 4-space indents, as well as tab characters. This normalizes everything to 4-space indents only, which is the standard Julia style, and is what's recommended in the JuMP style guide. Fixes #240.
ararslan
added a commit
that referenced
this issue
Nov 7, 2018
The package currently uses a mixture of indentation, including 2- and 4-space indents, as well as tab characters. This normalizes everything to 4-space indents only, which is the standard Julia style, and is what's recommended in the JuMP style guide. Fixes #240.
ararslan
added a commit
that referenced
this issue
Nov 8, 2018
The package currently uses a mixture of indentation, including 2- and 4-space indents, as well as tab characters. This normalizes everything to 4-space indents only, which is the standard Julia style, and is what's recommended in the JuMP style guide. Fixes #240.
ararslan
added a commit
that referenced
this issue
Nov 8, 2018
The package currently uses a mixture of indentation, including 2- and 4-space indents, as well as tab characters. This normalizes everything to 4-space indents only, which is the standard Julia style, and is what's recommended in the JuMP style guide. Fixes #240.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally posted by @chriscoey in #239 (comment)
The text was updated successfully, but these errors were encountered: