Skip to content

fix link to scala compat for java 8 (again). #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 30, 2014
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion news/_posts/2014-06-30-2.12-roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Here’s how we plan to make this transition as smooth as possible.
## Features exclusive to Scala 2.12: more Java 8 fun
Development of the following features starts in 2015. Since they are binary incompatible, they can’t be backported to 2.11.

* Turn FunctionN into [Functional Interfaces](http://docs.oracle.com/javase/8/docs/api/java/lang/FunctionalInterface.html), so that Java 8 code can call higher-order methods in Scala without a [wrapper](https://github.com/typesafehub/scala-java8-fun).
* Turn FunctionN into [Functional Interfaces](http://docs.oracle.com/javase/8/docs/api/java/lang/FunctionalInterface.html), so that Java 8 code can call higher-order methods in Scala without a [wrapper](https://github.com/scala/scala-java8-compat).
* Support for @interface traits, which are guaranteed to compile to Java interfaces (useful for interop, performance and binary compatibility). This is a generalization of the above feature.
* Streams: integrate into Scala collections? (Anywhere from providing converters to replacing existing functionality.)
* Use the JDK’s forkjoin library instead of embedding our own. (Switch the global default ExecutionContext to be backed by the ForkJoinPool.commonPool().)
Expand Down