diff options
author | Eugene Burmako <xeno.by@gmail.com> | 2013-01-07 07:42:38 +0300 |
---|---|---|
committer | Eugene Burmako <xeno.by@gmail.com> | 2013-01-09 08:10:46 +0100 |
commit | 66acf364ae3003dd1abb4eeb8759afc6e12aa1a1 (patch) | |
tree | 853fc3cf39bd34ec32887843fb98f05bad8f1fb7 /test/files/run/hashsetremove.check | |
parent | d17e3fc29cd48a3d4cbbbfc1fc9eb021d787d4d7 (diff) | |
download | scala-66acf364ae3003dd1abb4eeb8759afc6e12aa1a1.tar.gz scala-66acf364ae3003dd1abb4eeb8759afc6e12aa1a1.tar.bz2 scala-66acf364ae3003dd1abb4eeb8759afc6e12aa1a1.zip |
SI-5903 extractor macros do work
Apparently it is already possible to use macros to customize pattern
matching as described in the comments to the aforementioned JIRA issue.
What's even better - with the incoming addition of c.introduceTopLevel
it becomes possible to generate arbitrarily complex unappliers, even
with heterogeneous types of arguments varying from expansion to expansion
Diffstat (limited to 'test/files/run/hashsetremove.check')
0 files changed, 0 insertions, 0 deletions