-
Notifications
You must be signed in to change notification settings - Fork 37
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
Single space inserted after function names #30
Comments
Why, I like to have a space there? |
It's non-standard formatting for D code, as you can see in druntime. |
As you can see in druntime and Phobos, there really is no standard. |
While there are no doubt uses of the space here and there, the vast majority of function declarations, something like 97%+, don't use one. That's fairly standard. |
What about adding a command line switch to control that behavior? E.g. |
That really isn't |
Actually, I don't mind changing the format of the output. I've changed my mind and is starting to use the style without the space in my own code. |
Well, so I'll assume that there is no point of adding switches to control the formatting to DStep (however we could change the behavior to not to place that space after function name, I prefer that variant more too). |
And there might be problem with pipeing the output to the other program, as DStep doesn't print its output to stdout and what is more it can output multiple files... |
That can be improved.
You can run dfmt after DStep has written the files 😉 |
Fix jacob-carlborg#30: Single space inserted after function names.
Fix jacob-carlborg#30: Single space inserted after function names.
Fix jacob-carlborg#30: Single space inserted after function names.
It gets inserted between a function name and the opening parenthesis for its parameters and even for function pointer declarations, please remove it.
The text was updated successfully, but these errors were encountered: