-
Notifications
You must be signed in to change notification settings - Fork 65
// comments instead of /* .. */ #16
Comments
👍 Where's the PR @drnic? |
Want to know if it's ok or if authors have some overriding preference. On Sat, Apr 26, 2014 at 2:35 PM, Joe Fitzgerald notifications@github.com
|
I'm fine trusting interested Go users on this one. |
@drnic Pull request to 🚀 please – this is bugging me also. |
Further references supporting the desire to prefer
In summary, it the vast majority of your comments are likely to be line-style. Block-style comments may occasionally be seen in package comments, but even then only in non-trivial packages (likely with examples). Consequently, |
@nathansobo I'm looking across a couple of packages - not sure what it is that defines the comment type for Cmd+/ - can you point me to some examples? |
I think that's just defining that /* ... */ is a valid multi-level comment On Mon, Apr 28, 2014 at 9:50 AM, Joe Fitzgerald notifications@github.comwrote:
Dr Nic Williams |
When you comment the editor wraps the text in |
@drnic Looks like scoped-properties = deliverance: https://github.com/atom/language-yaml/blob/master/scoped-properties/language-yaml.cson#L3 |
💄 Default To Line-Comments Style - Fixes #16
It seems more common for Go programs/libraries (esp samples shown at gophercon this week) use single line // comments rather than multiline /* ... */ comments. Can we change?
The text was updated successfully, but these errors were encountered: