diff options
author | Eugene Burmako <xeno.by@gmail.com> | 2014-01-30 10:01:31 +0300 |
---|---|---|
committer | Eugene Burmako <xeno.by@gmail.com> | 2014-02-14 23:51:22 +0100 |
commit | 114c99691674873393223a11a9aa9168c3f41d77 (patch) | |
tree | d855c67a565faf4dbe414cc8f1a1aaff68a8df79 /test/files/scalacheck/range.scala | |
parent | 27805570cbf130260eab04fe1491e58fa95e8108 (diff) | |
download | scala-114c99691674873393223a11a9aa9168c3f41d77.tar.gz scala-114c99691674873393223a11a9aa9168c3f41d77.tar.bz2 scala-114c99691674873393223a11a9aa9168c3f41d77.zip |
establishes scala.reflect.api#internal
Reflection API exhibits a tension inherent to experimental things:
on the one hand we want it to grow into a beautiful and robust API,
but on the other hand we have to deal with immaturity of underlying mechanisms
by providing not very pretty solutions to enable important use cases.
In Scala 2.10, which was our first stab at reflection API, we didn't
have a systematic approach to dealing with this tension, sometimes exposing
too much of internals (e.g. Symbol.deSkolemize) and sometimes exposing
too little (e.g. there's still no facility to change owners, to do typing
transformations, etc). This resulted in certain confusion with some internal
APIs living among public ones, scaring the newcomers, and some internal APIs
only available via casting, which requires intimate knowledge of the
compiler and breaks compatibility guarantees.
This led to creation of the `internal` API module for the reflection API,
which provides advanced APIs necessary for macros that push boundaries
of the state of the art, clearly demarcating them from the more or less
straightforward rest and providing compatibility guarantees on par with
the rest of the reflection API.
This commit does break source compatibility with reflection API in 2.10,
but the next commit is going to introduce a strategy of dealing with that.
Diffstat (limited to 'test/files/scalacheck/range.scala')
0 files changed, 0 insertions, 0 deletions