diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2013-10-29 16:04:17 +0100 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2013-11-08 08:20:45 +0100 |
commit | 3dba9932fcc79ce0ea6f7c9282320c14c95d133f (patch) | |
tree | ae37afaf2212d41706bb3f760bd2b4a5a8ff1925 /test/files/run/t6309.check | |
parent | 4aeb8acf99493a5b3f7c2e012796ded77ae40a7f (diff) | |
download | scala-3dba9932fcc79ce0ea6f7c9282320c14c95d133f.tar.gz scala-3dba9932fcc79ce0ea6f7c9282320c14c95d133f.tar.bz2 scala-3dba9932fcc79ce0ea6f7c9282320c14c95d133f.zip |
Add a per-run cache for member symbols
We are all used to calls to `definitions.PredefModule`, or
`defintions.Predef_???` to grab the symbol of some well known
entity. But you'll notice that some of these are lazy vals,
and others are defs.
Why is this so? In the presentation compiler, a member like
`Predef.???` will be assigned a new symbol after the user
browses into `Predef.scala`.
Mistakenly using vals in definitions leads to subtle
IDE bugs like SI-7678. We are able to trigger these
situations in tests, as noted in the comments of that issue.
Changing the vals to defs, on the other hand, has a performance
penalty. Some schemes to workaround this have shown up:
cache them per-implicit search, or compare method names and owners
rather than symbols on hot paths in the type checker.
This commit introduces a facility to cache these sort of symbols
per-run, and uses it to check for `Predef.conforms` and
and for the class/type tag materializers.
A followup pull request (WIP: https://github.com/retronym/scala/compare/ticket/7678-2)
will expand the use of to address the widespread and unsafe caching
of member symbols that I found while investigating SI-7678.
Diffstat (limited to 'test/files/run/t6309.check')
0 files changed, 0 insertions, 0 deletions