the ultimate scala cheat sheet

the sheet says
"Automatically boxed and unboxed, no special handling like in java (->
int/Integer)"
right next to it. you can write scala code as if there was no jvm level
distinction between int and integer, but at runtime, there still is. i
think that nails it.

Am 25.01.2012 22:02, schrieb Daniel Sobral:
> I don't like calling the value classes "primitives", because it
> implies the distinction Java has and Scala doesn't.
>
> On Wed, Jan 25, 2012 at 18:30, HamsterofDeath wrote:
>> rapidshare lies, i can download it.
>>
>> Am 25.01.2012 20:45, schrieb Daniel Sobral:
>>> It told me the file was not available.
>>>
>>> On Wed, Jan 25, 2012 at 17:34, HamsterofDeath wrote:
>>>> since no one objected, here's the whole thing as a pdf:
>>>> https://rapidshare.com/files/3045603786/scc.pdf
>>>>
>>>>
>>>> Am 20.01.2012 21:54, schrieb HamsterofDeath:
>>>>> i did some research and wrote an example showing how implicits are
>>>>> resolved. take a look at it and if there is a mistake, please notify me :)
>>>>>
>>>>> https://gist.github.com/1649497
>>>>>
>>>>> Am 21.12.2011 21:02, schrieb HamsterofDeath:
>>>>>> hi community,
>>>>>>
>>>>>> i felt the desire to put together a scala cheat sheet. the reason is
>>>>>> that even after two years, i still find new features/tricks which don't
>>>>>> seem to be clearly documented - they exist, but are scattered across the
>>>>>> internet. there is already a cheat sheet, but it only covers a fraction
>>>>>> of what i am imagining here. there are some examples on scala-lang, but
>>>>>> i had to read them several times since they are not very clear. there
>>>>>> are some good blogs, but again, you have to look for them. i believe
>>>>>> that having a single, well structured pdf will make people more
>>>>>> comfortable with scala if they are new, should make it easier to
>>>>>> convince heretics to believe in scala :) and take away the fear of the
>>>>>> unknown complexity.
>>>>>>
>>>>>> it's probably going to be bigger than the usual cheat sheet so it's more
>>>>>> like a wallpaper, but splitting it up into subsections should help.
>>>>>> also, i want to focus on productivity boost features and keep it on a
>>>>>> level that a random java dev should be able to understand (i am thinking
>>>>>> about avoiding scary method signatures here and use java code as
>>>>>> examples of how this would look like in java or maybe other languages as
>>>>>> well)
>>>>>>
>>>>>> send your findings/knowledge to me/this list :)
>>>>>> i'll collect them and put them together.
>>>>>>
>>>
>
>

I don't like calling the value classes "primitives", because it
implies the distinction Java has and Scala doesn't.

On Wed, Jan 25, 2012 at 18:30, HamsterofDeath <h-star [at] gmx [dot] de> wrote:
> rapidshare lies, i can download it.
>
> Am 25.01.2012 20:45, schrieb Daniel Sobral:
>> It told me the file was not available.
>>
>> On Wed, Jan 25, 2012 at 17:34, HamsterofDeath <h-star [at] gmx [dot] de> wrote:
>>> since no one objected, here's the whole thing as a pdf:
>>> https://rapidshare.com/files/3045603786/scc.pdf
>>>
>>>
>>> Am 20.01.2012 21:54, schrieb HamsterofDeath:
>>>> i did some research and wrote an example showing how implicits are
>>>> resolved. take a look at it and if there is a mistake, please notify me :)
>>>>
>>>> https://gist.github.com/1649497
>>>>
>>>> Am 21.12.2011 21:02, schrieb HamsterofDeath:
>>>>> hi community,
>>>>>
>>>>> i felt the desire to put together a scala cheat sheet. the reason is
>>>>> that even after two years, i still find new features/tricks which don't
>>>>> seem to be clearly documented - they exist, but are scattered across the
>>>>> internet. there is already a cheat sheet, but it only covers a fraction
>>>>> of what i am imagining here. there are some examples on scala-lang, but
>>>>> i had to read them several times since they are not very clear. there
>>>>> are some good blogs, but again, you have to look for them. i believe
>>>>> that having a single, well structured pdf will make people more
>>>>> comfortable with scala if they are new, should make it easier to
>>>>> convince heretics to believe in scala :) and take away the fear of the
>>>>> unknown complexity.
>>>>>
>>>>> it's probably going to be bigger than the usual cheat sheet so it's more
>>>>> like a wallpaper, but splitting it up into subsections should help.
>>>>> also, i want to focus on productivity boost features and keep it on a
>>>>> level that a random java dev should be able to understand (i am thinking
>>>>> about avoiding scary method signatures here and use java code as
>>>>> examples of how this would look like in java or maybe other languages as
>>>>> well)
>>>>>
>>>>> send your findings/knowledge to me/this list :)
>>>>> i'll collect them and put them together.
>>>>>
>>
>>
>



--
Daniel C. Sobral

I travel to the future all the time.

tw [at] mail [dot] gmail [dot] com" type="cite">
I see you're running Jekyll on Windows, I had problems before using jekyll on this os
and they went away with a reinstall  of Jekyll, Ruby and dependencies with a slightly different version mix.

tw [at] mail [dot] gmail [dot] com" type="cite">
You might be able to use Github pages http://pages.github.com/
to render your fork, I've done it before with another project,
this way you don't have to install anything else other than git.

ML

2012/1/7 Miller Heather <heather [dot] miller [at] epfl [dot] ch" rel="nofollow">heather [dot] miller [at] epfl [dot] ch>

On Jan 7, 2012, at 11:15 PM, HamsterofDeath wrote:

> Am 07.01.2012 23:03, schrieb Miller Heather:
>> Hi,
>>
>>> i am stuck. i was told to compile my stuff and take a look at the result
>>> before creating a pull request.
>> Very very very sound advice :)
>>
>>> i followed the instructions, but i get
>>> this error message:
>> I don't see anything useful in the below- usually Jekyll returns a more verbose error above the stack trace. I just forked your repo and tried to build it and at least in my case (from the most recently committed version in your repo, 5 days ago) it looks like you've confused jekyll into thinking you've got a head with two columns somewhere, though no idea where.
>
> why don't i see any errors when previewing my page online?

Read the list of errors that are generated above the stack trace- this is what I'm referring to. To repeat- regardless, I think the problem would be most quickly resolved by starting fresh with the original cheat sheet on docs.scala-lang, adding sections one-by-one, and incrementally building. This is the normal approach, whether your generating documentation or writing code, so it makes sense, right?

>>
>> Regardless, the best thing to do is to perhaps start clean, add sections from your version of the cheatsheet one-by-one, and incrementally build. I would also suggest submitting a clean pull-request eventually as well.
> what's the difference between a clean pull request and a "normal" one?

A clean one is from scratch. Have a look at the workflow for submitting scaladoc pull requests- it's the same in the case of docs.scala-lang.org, with the only difference being that the repository URL is different. In particular, it's a good idea to create a topic branch. See: https://wiki.scala-lang.org/display/SW/Workflow#Workflow-SubmittinggithubPullRequests

There are a few dozen commits in your current pull request, and it can't be automatically be merged as it is. Which, for me and other docs.scala-lang maintainers, is a big hassle to have to deal with on our end.

Cheers,
Heather


>
>>
>> Cheers,
>> Heather
>>
>>
>>> S:\scala_github\HamsterofDeath-scala.github.com-671225d>jekyll --server
>>> C:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
>>> iconv will be deprecated in the future, use String#encode in
>>> stead.
>>> Configuration from
>>> S:/scala_github/HamsterofDeath-scala.github.com-671225d/_config.yml
>>> Building site: S:/scala_github/HamsterofDeath-scala.github.com-671225d
>>> -> S:/scala_github/HamsterofDeath-scala.github.com-671225d/
>>> _site
>>> C:/Ruby193/lib/ruby/1.9.1/psych.rb:154:in `parse': (<unknown>): couldn't
>>> parse YAML at line 3 column 20 (Psych::SyntaxError)
>>>       from C:/Ruby193/lib/ruby/1.9.1/psych.rb:154:in `parse_stream'
>>>       from C:/Ruby193/lib/ruby/1.9.1/psych.rb:125:in `parse'
>>>       from C:/Ruby193/lib/ruby/1.9.1/psych.rb:112:in `load'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/convertible.rb:33:in
>>> `read_yaml'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/page.rb:24:in
>>> `initialize'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:140:in
>>> `new'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:140:in
>>> `block in read_directories'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:130:in
>>> `each'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:130:in
>>> `read_directories'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:135:in
>>> `block in read_directories'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:130:in
>>> `each'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:130:in
>>> `read_directories'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:98:in
>>> `read'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/site.rb:38:in
>>> `process'
>>>       from
>>> C:/Ruby193/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/bin/jekyll:250:in
>>> `<top (required)>'
>>>       from C:/Ruby193/bin/jekyll:19:in `load'
>>>       from C:/Ruby193/bin/jekyll:19:in `<main>'
>>>
>>> my experience considering ruby, YAML, jekyll or whatever i'm doing there
>>> is zero. i just blindly followed some readme. how can i fix this?
>>>
>>> Am 21.12.2011 21:02, schrieb HamsterofDeath:
>>>> hi community,
>>>>
>>>> i felt the desire to put together a scala cheat sheet. the reason is
>>>> that even after two years, i still find new features/tricks which don't
>>>> seem to be clearly documented - they exist, but are scattered across the
>>>> internet. there is already a cheat sheet, but it only covers a fraction
>>>> of what i am imagining here. there are some examples on scala-lang, but
>>>> i had to read them several times since they are not very clear. there
>>>> are some good blogs, but again, you have to look for them. i believe
>>>> that having a single, well structured pdf will make people more
>>>> comfortable with scala if they are new, should make it easier to
>>>> convince heretics to believe in scala :) and take away the fear of the
>>>> unknown complexity.
>>>>
>>>> it's probably going to be bigger than the usual cheat sheet so it's more
>>>> like a wallpaper, but splitting it up into subsections should help.
>>>> also, i want to focus on productivity boost features and keep it on a
>>>> level that a random java dev should be able to understand (i am thinking
>>>> about avoiding scary method signatures here and use java code as
>>>> examples of how this would look like in java or maybe other languages as
>>>> well)
>>>>
>>>> send your findings/knowledge to me/this list :)
>>>> i'll collect them and put them together.
>>>>
>>
>

0Fosz0c3ewR5xdWEj-TW3ZQZFiRvcYburTws02w [at] mail [dot] gmail [dot] com" type="cite">Hi great work!

I wanted to report just a few typos I found:

def method(s:String)(s2:String) = s+" "+s2)

0Fosz0c3ewR5xdWEj-TW3ZQZFiRvcYburTws02w [at] mail [dot] gmail [dot] com" type="cite">
"=" means modify mutable collection xor assign new immutable collection to var

0Fosz0c3ewR5xdWEj-TW3ZQZFiRvcYburTws02w [at] mail [dot] gmail [dot] com" type="cite">
"comma separated numbers: " + List(1, 2, 3, 4, 5).fold("0")(_ + ", " + _)  // Should be just "" instead of "0".

0Fosz0c3ewR5xdWEj-TW3ZQZFiRvcYburTws02w [at] mail [dot] gmail [dot] com" type="cite">
class CoVariant[-A] // Should be ContraVariant

0Fosz0c3ewR5xdWEj-TW3ZQZFiRvcYburTws02w [at] mail [dot] gmail [dot] com" type="cite">
class having a contravariant type parameter, meaning val CoVariant[SubClass] = coVariantWithSuperclass compiles

0Fosz0c3ewR5xdWEj-TW3ZQZFiRvcYburTws02w [at] mail [dot] gmail [dot] com" type="cite">
On Fri, Dec 23, 2011 at 6:36 PM, HamsterofDeath <h-star [at] gmx [dot] de" rel="nofollow">h-star [at] gmx [dot] de> wrote:

what i got so far

https://github.com/HamsterofDeath/scala.github.com/blob/gh-pages/cheatsheets/index.md

if you find an error, report it to me.
todos:
option
tuples
pattern matching, apply, unapply
objects, companion objects
abstract types
implicit conversions




Am 22.12.2011 07:40, schrieb HamsterofDeath:

i'll put that right at the top. what about val 1 = "hello number"?

Am 21.12.2011 23:59, schrieb Som Snytt:

Thanks for the link!

But for some reason, it starts with
val x = 5
instead of
val 1 = 2

:)

On Wed, Dec 21, 2011 at 12:16 PM, Daniel Sobral <dcsobral [at] gmail [dot] com" target="_blank" rel="nofollow">dcsobral [at] gmail [dot] com> wrote:

You do know http://docs.scala-lang.org/cheatsheets/, I assume? Please,
do contribute to it if you think there's things missing in it. You can
contribute directly through this link:
https://github.com/scala/scala.github.com/blob/gh-pages/cheatsheets/index.md

On Wed, Dec 21, 2011 at 18:02, HamsterofDeath <h-star [at] gmx [dot] de" target="_blank" rel="nofollow">h-star [at] gmx [dot] de> wrote:
> hi community,
>
> i felt the desire to put together a scala cheat sheet. the reason is
> that even after two years, i still find new features/tricks which don't
> seem to be clearly documented - they exist, but are scattered across the
> internet. there is already a cheat sheet, but it only covers a fraction
> of what i am imagining here. there are some examples on scala-lang, but
> i had to read them several times since they are not very clear. there
> are some good blogs, but again, you have to look for them. i believe
> that having a single, well structured pdf will make people more
> comfortable with scala if they are new, should make it easier to
> convince heretics to believe in scala :) and take away the fear of the
> unknown complexity.
>
> it's probably going to be bigger than the usual cheat sheet so it's more
> like a wallpaper, but splitting it up into subsections should help.
> also, i want to focus on productivity boost features and keep it on a
> level that a random java dev should be able to understand (i am thinking
> about avoiding scary method signatures here and use java code as
> examples of how this would look like in java or maybe other languages as
> well)
>
> send your findings/knowledge to me/this list :)
> i'll collect them and put them together.



--
Daniel C. Sobral

I travel to the future all the time.