diff options
| author | Eugene Burmako <xeno.by@gmail.com> | 2014-02-21 22:24:21 +0100 |
|---|---|---|
| committer | Eugene Burmako <xeno.by@gmail.com> | 2014-02-21 22:24:32 +0100 |
| commit | 64edb44fc6a4db0ba3ecee0555212d8112a17f1a (patch) | |
| tree | 908712ca8bb1a03820fa0b6e1a407e6f34fc7bc3 /test/files/neg/macro-bundle-wrongcontext-b.check | |
| parent | da1032caa4ee4c780b5fff3056dd816623a53737 (diff) | |
| download | scala-64edb44fc6a4db0ba3ecee0555212d8112a17f1a.tar.gz scala-64edb44fc6a4db0ba3ecee0555212d8112a17f1a.tar.bz2 scala-64edb44fc6a4db0ba3ecee0555212d8112a17f1a.zip | |
more helpful bundle error messages
At the moment, bundle selection mechanism is pretty picky. If a candidate
bundle's parameter isn't either blackbox.Context, whitebox.Context or
PrefixType refinement thereof, then it's not a bundle and the user
will get a generic error.
However we can be a bit more helpful and admit classes that are almost
like bundles (looksLikeMacroBundleType), have them fail isMacroBundleType,
and then emit a much prettier error message to the user that would tell them
that bundles must be monomorphic and their sole parameter should not just
be any subtype of blackbox.Context or whitebox.Context.
Diffstat (limited to 'test/files/neg/macro-bundle-wrongcontext-b.check')
| -rw-r--r-- | test/files/neg/macro-bundle-wrongcontext-b.check | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/files/neg/macro-bundle-wrongcontext-b.check b/test/files/neg/macro-bundle-wrongcontext-b.check index 9c94c3bc34..e9700d379e 100644 --- a/test/files/neg/macro-bundle-wrongcontext-b.check +++ b/test/files/neg/macro-bundle-wrongcontext-b.check @@ -1,4 +1,4 @@ -macro-bundle-wrongcontext-b.scala:10: error: not found: value Bundle +macro-bundle-wrongcontext-b.scala:10: error: macro bundles must be concrete monomorphic classes having a single constructor with a `val c: Context` parameter def foo: Any = macro Bundle.impl ^ one error found |