diff options
| author | Eugene Burmako <xeno.by@gmail.com> | 2012-08-17 15:49:38 +0200 |
|---|---|---|
| committer | Eugene Burmako <xeno.by@gmail.com> | 2012-08-18 09:00:55 +0200 |
| commit | ac430ac8ba554d1b976d44598400d95ce5cf3816 (patch) | |
| tree | 92f709ec56cca5895cd960e82a1ebd10a34ad98a /test/pending/neg/macro-invalidusage-badbounds-b.check | |
| parent | 7fc860963a4f76cb18e44c20f2bdfb49641033f3 (diff) | |
| download | scala-ac430ac8ba554d1b976d44598400d95ce5cf3816.tar.gz scala-ac430ac8ba554d1b976d44598400d95ce5cf3816.tar.bz2 scala-ac430ac8ba554d1b976d44598400d95ce5cf3816.zip | |
cleanup for macroExpand
Error reporting is moved to ContextErrors to disentangle stuff in Macros.scala.
With logics and error reporting intertwined it was an awful mess.
Exceptions are used for the same reason. Instead of threading failures through
the code polluting it with options/ifs, I outline the success path.
It worked much better for typedMacroBody, but I'm also happy with the resulting
code of macroExpand. To me a major factor towards applicability of exceptions
was that they are short-lived and that there might be max one error per domain,
after which we unconditionally bail.
Diffstat (limited to 'test/pending/neg/macro-invalidusage-badbounds-b.check')
| -rw-r--r-- | test/pending/neg/macro-invalidusage-badbounds-b.check | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/test/pending/neg/macro-invalidusage-badbounds-b.check b/test/pending/neg/macro-invalidusage-badbounds-b.check new file mode 100644 index 0000000000..fd0b64533e --- /dev/null +++ b/test/pending/neg/macro-invalidusage-badbounds-b.check @@ -0,0 +1,4 @@ +Macros_Test_2.scala:7: error: type arguments [Int] do not conform to macro method foo's type parameter bounds [U <: String]
+ foo[Int]
+ ^
+one error found
|