diff options
author | Eugene Burmako <xeno.by@gmail.com> | 2013-03-30 10:41:04 +0700 |
---|---|---|
committer | Eugene Burmako <xeno.by@gmail.com> | 2013-05-11 18:37:10 +0200 |
commit | bb73b9669a96410bc9c513d061d090f5bd3c075e (patch) | |
tree | 23b5a3f29b04f52dd403e17d349694f18a09486b /starr.number | |
parent | 90ac5c4e1350493f6f47c674572c2dcb97b2b9eb (diff) | |
download | scala-bb73b9669a96410bc9c513d061d090f5bd3c075e.tar.gz scala-bb73b9669a96410bc9c513d061d090f5bd3c075e.tar.bz2 scala-bb73b9669a96410bc9c513d061d090f5bd3c075e.zip |
[nomaster] macroExpandAll is now triggered in all invocations of typed
macroExpandAll is the key player in the mechanism of expanding macros after
their type arguments have been inferred. (Macro applications that contain
yet uninferred type arguments don't get expanded and are delayed until
the targs are inferred. Therefore later on we need to trigger those delayed
expansions manually, which is done by macroExpandAll).
Previously macroExpandAll was only called from a few selected places in
the typechecker, but that's quite risky, since typer evolves, and who knows
when this scheme breaks.
To make things more robust, I'm now calling macroExpandAll in the epilogue
of every single call to `typed`. Don't worry - this shouldn't impose
noticeable performance penalties, since the call is guarded by a branch
upon a plain boolean field.
NOTE: This patch is a second take on fixing implicit macros, with the first
one being a backport from macro paradise merged into master in January 2013:
https://github.com/scala/scala/commit/fe60284769.
The original fix had an unfortunate error, as described on scala-internals:
https://groups.google.com/forum/#!msg/scala-internals/7pA9CiiD3u8, so I had
to refine the approach here.
This means that it's not possible to directly merge this commit into master,
so I'm marking it as [nomaster] and will submit a separate pull request
targetting master later on.
Diffstat (limited to 'starr.number')
0 files changed, 0 insertions, 0 deletions