I'm not sure what your point is either. Mine was "oh, there's a website now; they must have been reviewing old issues to prepare for the launch." There is no "official" style guide, you're 100% right, but I'm not sure what that has to do with this.
It's actually an interesting thread. My take would have been to use comma when it's something we intend to modify, no comma when it's not. So intent is explicit.
Comments
I made a comment on this thread[1] in 2014, and it was closed two days ago. I wondered why... guess this is why!
1: https://github.com/rubocop-hq/ruby-style-guide/issues/273
This thread is interesting to me, since I've changed my mind on this topic since I originally commented. :P
I blame Rust, and macros.
I don’t fully get your point. There is no official style guideline for Ruby.
I'm not sure what your point is either. Mine was "oh, there's a website now; they must have been reviewing old issues to prepare for the launch." There is no "official" style guide, you're 100% right, but I'm not sure what that has to do with this.
Oh, got you. I thought you were implying some conspiracy to kill conversation or something. Nvm.
Ah, yeah, no worries! I was not :)
It's actually an interesting thread. My take would have been to use comma when it's something we intend to modify, no comma when it's not. So intent is explicit.
Like:
Yeah, you're right. I was triaging and cleaning up the open issues prior to launching the new site.
Now that the guide has more editors I'm optimistic that we won't end up in a situation with that many non-triaged tickets down the road.