Blog implicit functions v2 #571
Conversation
|
I somehow can't add these things without getting a conflict. Not sure where that comes from. All I did was enable disqs and add one sentence to the end. Can someone help me get this in? Thanks! |
|
Let's not use Disqus. Let's point people at Discourse instead. WDYT? |
|
needs a rebase on current master — the filename has changed, it's now the front matter at the top of the file has also changed, that change was necessary in order to get the post to show up at all. |
I had been thinking about suggesting that as well. It's a bit weird because Discourse isn't really totally announced & launched yet, but the cat is already out of the bag in multiple places (the SPP announcement, the latest Scala Center advisory board minutes, many mentions in multiple Gitter rooms, etc), so yeah, I'd be comfortable with including a Discourse link |
|
I think it's OK that we haven't made a formal announcement yet. I rather prefer that people start organically using it first, so we have some activity first. I'm ready to announce it, I was just waiting for people to get a feel for it and for us to work some bugs out. |
|
I thought of doing that but was not sure what the intended audience is.
Someone who is not a contributor might still want to comment, would
Discourse be the right forum for them?
- Martin
…On Wed, Dec 7, 2016 at 8:25 PM, Heather Miller ***@***.***> wrote:
I think it's OK that we haven't made a formal announcement. I rather
prefer that people start organically using it first, so we have some
activity first. I'm ready to announce it, I was just waiting for people to
get a feel for it and for us to work some bugs out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#571 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAwlVrAVPGUaO0BUMJ0awVTwOpseT0gAks5rFxZUgaJpZM4LHDXu>
.
--
Martin Odersky
EPFL and Lightbend
|
My take on this is that anyone with an intelligent comment to make about a proposed Scala language change is a contributor. Discourse is new for Scala so the signaling around it isn't very clear yet, but think that choosing to post to contributors.scala-lang.org over users.scala-lang.org will tend to signal that a higher level of knowledge and discourse is expected, and for a blog post like this, that seems fine to me. For a different kind of blog post — I don't know, maybe one asking about Scala adoption at companies, or about the getting-started experience — I could imagine choosing users.scala-lang.org instead for the comment thread. |
|
as a PR, this is superseded by #573 |
No description provided.