Scala.js 0.5.2 release

Author: gzm0

_config.yml

@@ -18,7 +18,7 @@ author :
  twitter : sjrdoeraene
  feedburner : feedname
 
-scalaJSVersion: 0.5.1
+scalaJSVersion: 0.5.2
 scalaJSBinaryVersion: 0.5
 
 # The production_url is only used when full-domain names are needed

_posts/news/2014-07-09-announcing-scalajs-0.5.2.md

@@ -0,0 +1,47 @@
+---
+layout: post
+title: Announcing Scala.js 0.5.2
+category: news
+tags: [releases]
+---
+{% include JB/setup %}
+
+We are excited to announce the release of Scala.js 0.5.2!
+
+Scala.js 0.5.2 is backward binary compatible with older versions of the 0.5.x branch. However, it is *not* forward binary compatible. This means:
+
+- You don't need to re-publish libraries
+- You must upgrade to Scala.js 0.5.2 if any library you depend on uses Scala.js 0.5.2
+
+If you choose to re-publish a library, make sure to bump its version.
+
+Please report any issues [on GitHub](https://github.com/scala-js/scala-js/issues).
+
+## Improvements in the 0.5.2 release
+
+For changes introduced in 0.5.0, how to upgrade, getting started etc. have a look at the [0.5.0 announcement]({{ BASE_PATH }}/news/2014/06/13/announcing-scalajs-0.5.0/) (and maybe the [0.5.1 announcement]({{ BASE_PATH }}/news/2014/06/30/announcing-scalajs-0.5.1/)).
+
+#### TypedArrays
+
+The new package `scala.scalajs.js.typedarray` contains facade types
+for JavaScript TypedArrays. It introduces compiler support to convert
+`scala.Array`s to their TypedArray equivalent and vice versa.
+
+Note that TypedArrays are **not** part of the ECMAScript 5
+specification. You need to make sure your target platform supports
+TypedArrays in addition to ECMAScript 5, if you decide to use them. Scala.js'
+[TypedArray test suite](https://github.com/scala-js/scala-js/tree/v0.5.2/test-suite/src/test/scala/scala/scalajs/test/typedarray)
+covers the full typed API and should be sufficient to verify whether a
+given JavaScript runtime supports TypedArrays.
+
+#### Bugfixes
+
+The following bugs have been fixed in 0.5.2:
+
+- [#789](https://github.com/scala-js/scala-js/issues/789) `fastOptStage::run` fails with Node.js
+- [#791](https://github.com/scala-js/scala-js/issues/791) Default arguments in the constructor of facade classes fail if the companion object doesn't extend `js.Any`
+- [#796](https://github.com/scala-js/scala-js/issues/796) Extending `js.Any` directly gives strange error messages
+
+#### Changes to the IR
+
+Some minor changes have been made to the IR to better accommodate the incremental optimizer in the pipeline for 0.5.3. This is the reason for the lack of forward binary compatibility.

doc/index.md

@@ -31,6 +31,12 @@ Generated Scaladocs are available here:
 
 ### Scala.js
 
+#### Scala.js 0.5.2
+* [0.5.2 scalajs-library]({{ BASE_PATH }}/api/scalajs-library/0.5.2/#scala.scalajs.js.package)
+* [0.5.2 scalajs-tools]({{ BASE_PATH }}/api/scalajs-tools/0.5.2/)
+* [0.5.2 scalajs-test-bridge]({{ BASE_PATH }}/api/scalajs-test-bridge/0.5.2/)
+* [0.5.2 scalajs-jasmine-test-framework]({{ BASE_PATH }}/api/scalajs-jasmine-test-framework/0.5.2/)
+
 #### Scala.js 0.5.1
 * [0.5.1 scalajs-library]({{ BASE_PATH }}/api/scalajs-library/0.5.1/#scala.scalajs.js.package)
 * [0.5.1 scalajs-tools]({{ BASE_PATH }}/api/scalajs-tools/0.5.1/)

doc/semantics.md

@@ -16,12 +16,13 @@ exceptions. For information about how Scala numeric types map to
 JavaScript numeric types, have a look at the
 [interoparability guide](./js-interoperability.html).
 
-### Floats behave like Doubles
-Since JavaScript doesn't have a native float type, we represent them
-using doubles/numbers, rather than manually implementing float
-arithmetic.
+### Floats may behave like Doubles
+Since JavaScript doesn't have a native float type, we sometimes represent Floats
+using doubles/numbers, rather than with lower-precision 32-bit floats.
 
-Note that float literals are still truncated to their (binary)
+The choice of how to represent floats is up to the implementation. You may not rely on floats providing 64-bit floating point precision.
+
+Float literals are truncated to their (binary)
 precision. However, output does not truncate to that precision. This
 can lead to the following behavior (this works as expected when using
 doubles):

downloads.md

@@ -9,6 +9,12 @@ We strongly recommend using the SBT plugin, as shown in the [bootstrapping skele
 
 The CLI distribution requires `scala` and `scalac` (of the right major version) to be on the execution path. Unpack it wherever you like and add the `bin/` folder to your execution path.
 
+#### Scala.js 0.5.2
+* [0.5.2, Scala 2.11 (tgz, 14MB)]({{ BASE_PATH }}/files/scalajs_2.11-0.5.2.tgz)
+* [0.5.2, Scala 2.11 (zip, 14MB)]({{ BASE_PATH }}/files/scalajs_2.11-0.5.2.zip)
+* [0.5.2, Scala 2.10 (tgz, 15MB)]({{ BASE_PATH }}/files/scalajs_2.10-0.5.2.tgz)
+* [0.5.2, Scala 2.10 (zip, 15MB)]({{ BASE_PATH }}/files/scalajs_2.10-0.5.2.zip)
+
 #### Scala.js 0.5.1
 * [0.5.1, Scala 2.11 (tgz, 13MB)]({{ BASE_PATH }}/files/scalajs_2.11-0.5.1.tgz)
 * [0.5.1, Scala 2.11 (zip, 13MB)]({{ BASE_PATH }}/files/scalajs_2.11-0.5.1.zip)

index.md

@@ -16,7 +16,7 @@ Although this is a project of LAMP/EPFL for which we will continue to provide
 best-effort improvements and bug fixes, it is <i>not</i> supported by Typesafe,
 and not part of any of their support contracts. You have been warned!</p>
 
-<p style="text-align: center"><a href="{{ BASE_PATH }}/news/2014/06/30/announcing-scalajs-0.5.1/" class="btn btn-large btn-success">Latest stable release: 0.5.1</a></p>
+<p style="text-align: center"><a href="{{ BASE_PATH }}/news/2014/07/09/announcing-scalajs-0.5.2/" class="btn btn-large btn-success">Latest stable release: 0.5.2</a></p>
 
 Noteworthy features: