It'd be nice to have a list of people (as github user icons) under a subsection called "contributed by" on each page.

I came across a blog post by Andrew Forrest that says he has submitted an SIP on removing null from the language, but I don't see it on the list of SIPs. Has it vanished?

It'd be nice if there was a "Recent Updates" section on the front page.

At least in the case of the macros page, the table of contents block on the right does not match the table of contents page.

Is there one in progress right now? I'm new to Scala but have written enough Ruby that I have "legacy Ruby code" out there making people cry right now. I'd like to offer my help if someone's already writing one...

When reading the Tour of Scala on an iPhone 5, and I zoom in to the content so that the actual text fills the screen, the table of contents starts out in the right position, but when I scroll down, the table of contents jumps far to the right, almost off screen. It then stays offscreen even if I try to scroll to the right to see it. Combined with #390 it is really hard to read the Tour on an iPhone.

Initial position:

After scrolling down

My case class is：

case class IdentityId(userId: String, providerId: String)
case class IdentityItem (
userId:String,
providerID: String,
identityId:IdentityId)

I want to set the new initial value of identityId equal to IdentityId(userId,providerID) , This is similar to C++ initialize members of a class.
the whole code is like:

case class IdentityId(userId: String, providerId: String)
case class IdentityItem (
userId:String,
providerID: String,
identityId:IdentityId=IdentityId(userId,providerID))

The Scala Style Guide is an important document. At the moment it appears on many separate pages, which is great for browsing but not so good for printing out or for reading right through. It would be great if there was a single-page version available for these purposes.

I'm very happy to do the work necessary to make this happen, but I'm not sure where to start. Please can someone point me at the code that generates HTML from the .md pages in /style?

Thanks.

--KW 8-)

I and my friend have started translating the tutorial pages in Korean.

I create copies of the original tour markdown files into /ko/tutorials/tour. But it looks like the 'language' headers I added to the markdown docs do not automatically enable the language configuration on the sidebar.

How can I create a new small tiny national flag on the sidebar of the tour? Please help me!

It happened that Google guided me to a page of one of the (multi-page) Scala docs guides, e.g.
http://docs.scala-lang.org/overviews/parallel-collections/performance.html

I wanted to know in which guide I landed, but actually, the title is nowhere shown (except within the URL). I think the title should be locatable with a finite number of clicks. I propose to add the title of the guide
a) in the table of contents block (instead of the title "Contents" or in addition above the title); or
b) on the first page which currently has the title "Contents".

Having a Gemfile (α) in the root directory with a content as follows:

source :rubygems

gem "jekyll"
gem "RedCloth"

would make installation for users of bundler much easier.

# Installs all required gems into a local folder (β)
# Without --path it will try to install globally
$ bundle install --path=vendor/

# Run local version of jekyll 
$ bundle exec jekyll

In the long run this means less version conflicts and less binaries in $PATH.

(α) For build stability, Gemfile.lock could also be checked in. This will fix the version number of every gem.
(β) One might need to exclude vendor/ from Jekyll’s build system then.

The blog page is blank: http://www.scala-lang.org/blog/

This is both in the sense of the title of the actual window as well as the title of the page. Nowhere on the page does it say the title of the actual collection of documents.

Original suggestion:

Speaking of which, do you plan on writing an index.md for the guide?
If ppl bookmark the write up it'd say "Overview - Scala Documentation"
and nowhere on the page it says Scala Parallel Collections Guide. If
not maybe include the overview name as part of the title, maybe?

Disqus comments are not appearing for some reason. I am logged into Disqus.

For example, in the Scala Style Guide.

http://www.scala-lang.org/api/current/index.html#scala.collection.immutable.HashMap@foreach(f:A=>Unit):Unit
http://www.scala-lang.org/api/current/index.html#scala.collection.mutable.HashMap@foreach(f:A=>Unit):Unit

The source code for the HashMap -both mutable and immutable- does not agree with this.

As it stands, it's not possible to subscribe to the comment feeds on docs.scala-lang. It'd be nice to explore the idea of subscribing to all or some of the posts to the site.

Not sure if it's just me, but I spent the last few weeks frustrated by the lack of macro documentation in 2.10 until I realized today that the table of contents on the right-hand side of the page links to several other (very helpful) pages.

Is there any way to make it clearer that the reader is just looking at one page of the docs? Maybe Next and Prev links at the top and bottom?

Goal: Most useful information at the top, and honour the title of "Core: The essentials"

Suggestions:

• Move collections, futures/promises to to top
• move reflect/macros to a new sub-section ("experimental")
• move Scala Actor API to a new sub-section ("deprecated") (or maybe remove it altogether)

I'm not sure how to do this myself, otherwise I'd submit a PR. Any pointers, @heathermiller?

Some pages in the collections overview, for example have become outdated. It's up-to-date with respect to Scala 2.8, but not Scala 2.9-- in particular, there's no mention of the Gen traits that had to be introduced due to the introduction of parallel collections in 2.9.

Collections isn't the only place where this is the case. This is also an issue on other documents as well.

For reasons like these, it'd be nice to have a "ToDos" or "this doc needs some revisions" note on the page, with a list of what needs to be done-- so committers/community can make revisions as they find them.

The Scala Glossary is excellent, I just wish there was a way to link directly to one of its entries.

For example, when writing it would be great to link directly to the entry for "function literal" like this:
http://docs.scala-lang.org/glossary/#function_literal

Unfortunately this link just resolves to the top level of the glossary. Can this be fixed to support direct links to glossary entries?

This webpage does not appear to exist anymore:

http://www.ezresult.com/article/Lambda_calculus

It's been pointed to from here:

http://docs.scala-lang.org/tutorials/tour/case-classes.html

The ordering is correct on the index page, but incorrect when you navigate into the document.

Similar to #275

I'm new to scala, but very well versed in PHP. I'd be happy to help with any tutorial geared towards PHP devs.

The readme is out of date. It talks about manually managing Jekyll versions, but this is now handled automatically via Bundler. Bundler is not mentioned in the readme at all.
The screenshot to Mou is a broken link.

Need to make a place for Daniel to add his FAQs to.

The geoal is to have them have their own subsection on the doc-site (assuming FAQ pages keep being added). But it'd also be nice to give them a place on the front page- for example, two or three could randomly be chosen and displayed.

Under the title "Creating a Parallel Collection" (https://github.com/scala/scala.github.com/blob/master/overviews/parallel-collections/overview.md) I think this is wrong:

import scala.collection.parallel.mutable.ParArray
val pv = new ParVector[Int]

We've two options:

import scala.collection.parallel.immutable.ParVector
val pv = new ParVector[Int]

import scala.collection.parallel.immutable.ParArray
val pa = new ParArray[Int]

What do you think?

There's a broken link to LodgeIt (paste.pocoo.org) on the indentation page (search for "pipeline operator").

What is the preferred style of multiple import statements? I didn't find any documentation about this in the style guide.

The Scala cheatsheet has this example:

import scala.collection.{Vector, Sequence}

Which also seems to be the format IntelliJ prefers but scalariform enforces the following formatting:

import scala.collection.{ Vector, Sequence }

I personally prefer the first one.

I use slick 2.0.1

My case class is：

   case class IdentityId(userId: String, providerId: String)
   case class IdentityItem (
   userId:String,
   providerID: String,
   ....
   ){
   def identityId=IdentityId(userId,providerID)
  }

userId is the foreign key of user table, providerID is the foreign key of provider table, for avoid composite primary keys, I decide add another column name identityId.

you should know that in default slick use only constructed field as the datatable column. In this case I want to use additional column "identityId".

Hello friends,

i'm finishing the translation of this tutorial: https://github.com/scala/scala.github.com/blob/gh-pages/tutorials/scala-for-java-programmers.md

When discussing traits, the authors define this method:

override def equals(that: Any): Boolean = that.isInstanceOf[Date] && {
      val o = that.asInstanceOf[Date]
      o.day == day && o.month == month && o.year == year
}

Shouldn't be better to define the same method this way:

   override def equals(that: Any): Boolean = that match{
     case o:Date => o.day == day && o.month == month && o.year == year
     case _ => false
   }

Maybe a note can be added noting the type erasure problem.

What do you think?

There is arguably garbage around the headers in the documentation for quasiquotes. I am wondering if there is a specific reason for this or if no one ever bothered to report this and fix it.

It's minor, but apparently there is a domain-specific language note to reference in the Parentheses section of the Naming Conventions doc:

Methods which act as accessors of any sort (either encapsulating a field
or a logical property) should be declared *without* parentheses except
if they have side effects. While Ruby and Lift use a `!` to indicate
this, the usage of parens is preferred [\#dsl\_note]\_.

I cannot trace down what doc is supposed to be linked here.

-Ron

I was working through the great documentation on futures and came across a basic issue:

:13: error: not found: value Success
f onComplete { case Success(x) => println(x); case Failure(e) => println(s"failed: $e") }

After some googling it seems a refactor moved those values to a different location. Adding this import fixes things:

scala> import scala.util.{Success, Failure}

I started to add this to the markdown docs for a pull request, but wanted to see if just adding it to the top where the other imports are mentioned is best or if someone more familiar with this change and the docs has a better suggestion?

Would a quickref for collection methods be useful? I had one written down while learning the collection library where I tried to make it as compact as possible. It's mostly scala code but I had to resort to set notation for some sections and types are different too. May be too ad-hoc but putting it here as a suggestion. Maybe some alternative form can be used or quick "99 problems" examples highlighting each method.

Example can be found here.

The example at
http://docs.scala-lang.org/style/indentation.html#methods-with-numerous-arguments

is supposed to show when lines should be wrapped. However, lines 10 and 11 are wrapped again in my browser by the code display, and that makes the example unnecessarily hard to understand. Instead of:

val myOnerousAndLongFieldNameWithNoRealPoint = foo(someVeryLongFieldName,

you see

val myOnerousAndLongFieldNameWithNoRealPoint =
foo(someVeryLongFieldName,

If you're careful enough, you can notice that the continuation line lacks a line number, but it'd be better to avoid the wrapping.

The layout fixes the line length to which the code is wrapped — extending that would be a more invasive change. Hence it might be best to simply shorten the line.

See: http://docs.scala-lang.org/overviews/core/architecture-of-scala-collections.html

There should be no Spanish flag indicating that a Spanish translation exists-- because one doesn't.

Click on japanese version of guide

results in 404.

It is not clear why this icon presented, since we don't have such post in /ja.

We should replace to ClassTag

http://docs.scala-lang.org/overviews/collections/arrays.html
http://docs.scala-lang.org/tutorials/FAQ/context-and-view-bounds.html
http://docs.scala-lang.org/overviews/collections/concrete-mutable-collection-classes.html

http://docs.scala-lang.org/ja/overviews/collections/concrete-mutable-collection-classes.html
http://docs.scala-lang.org/ja/overviews/collections/arrays.html

The Naming Conventions on the Style guide does not cover constants, which has caused at least one person to comment to me on Stack Overflow that the correct style is camel case starting with a lower case character, as described in this section.

In all pages with a "Contents" menu, there is no script in place to stop the bottom of the Contents container from overlapping with the footer (when the list of Contents is large). An example is the entire Scala Tour: http://docs.scala-lang.org/tutorials/tour/implicit-parameters.html

http://docs.scala-lang.org/overviews/

First of all, it's not possible to click on the actual guides
Second of all, their sub pages are showing up as links

jekyll serve fails with following error. I am using ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux]

Not creating a link for ref_id = "msg_unit".  Liquid Exception: cannot load such file -- posix_spawn_ext in sip-tutorial.md
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/share/gems/gems/posix-spawn-0.3.6/lib/posix/spawn.rb:2:in `'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/share/gems/gems/pygments.rb-0.5.0/lib/pygments/popen.rb:2:in `'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/share/gems/gems/pygments.rb-0.5.0/lib/pygments.rb:1:in `'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/tags/highlight.rb:52:in `render_pygments'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/tags/highlight.rb:45:in `render'
/usr/local/share/gems/gems/liquid-2.5.0/lib/liquid/block.rb:106:in `block in render_all'
/usr/local/share/gems/gems/liquid-2.5.0/lib/liquid/block.rb:93:in `each'
/usr/local/share/gems/gems/liquid-2.5.0/lib/liquid/block.rb:93:in `render_all'
/usr/local/share/gems/gems/liquid-2.5.0/lib/liquid/block.rb:82:in `render'
/usr/local/share/gems/gems/liquid-2.5.0/lib/liquid/template.rb:124:in `render'
/usr/local/share/gems/gems/liquid-2.5.0/lib/liquid/template.rb:132:in `render!'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/convertible.rb:77:in `render_liquid'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/convertible.rb:128:in `do_layout'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/page.rb:111:in `render'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/site.rb:235:in `block in render'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/site.rb:233:in `each'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/site.rb:233:in `render'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/site.rb:44:in `process'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/command.rb:18:in `process_site'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/commands/build.rb:23:in `build'
/usr/local/share/gems/gems/jekyll-1.0.2/lib/jekyll/commands/build.rb:7:in `process'
/usr/local/share/gems/gems/jekyll-1.0.2/bin/jekyll:59:in `block (2 levels) in '
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/command.rb:180:in `call'
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/command.rb:180:in `call'
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/command.rb:155:in `run'
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/runner.rb:402:in `run_active_command'
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/runner.rb:78:in `run!'
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/delegates.rb:7:in `run!'
/usr/local/share/gems/gems/commander-4.1.3/lib/commander/import.rb:10:in `block in '
Build Failed

I noticed that there are no next/previous buttons in the Tour of Scala. This makes the tour a bit harder to read than it needs to be.

Would be nice if there was some place to aggregate quality external guides out there, like Twitter's Scala School, or Twitter's Effective Scala, amongst others.

This should be its own section, or be a subsection on individual pages if #36 would be implemented.

The first guide listed is the architecture of Scala collections. The overview of Scala collections appears further down (and with its full index -- that's bad too). People will naturally try the first resource they find, and they assume topics further up are more entry-level than topics further down.

It would be nice if concepts could each have their own central page on the site, indexing the articles and other bits of information we have about these concepts. For example, for something like implicit conversions could have a short content page introducing them (content like this could come from the Scala Tour), a section for examples, which people could contribute to, and a section connecting this concept with other related articles- implicits, for example, would have pointers to Daniel Sobral's FAQ pages on implicits.

On the style guide page [http://docs.scala-lang.org/style/], the link to overview [http://docs.scala-lang.org/style/overview.html] is broken. On any of the content pages, the sidebar is broken with the error:

**ERROR**. Couldn't find the total number of pages in this set of tutorial articles. Have you declared the `outof` tag in your YAML front matter?