From 810db8540f259407decb4557aece0dfec4e58a03 Mon Sep 17 00:00:00 2001 From: Adriaan Moors Date: Wed, 19 Feb 2014 20:58:52 -0800 Subject: SI-6675 deprecation warning for auto-tupling in patterns NOTE: when the deprecation warning becomes an error, SI-6111 must become a `won't fix` --- test/files/run/t6111.check | 1 + test/files/run/t6111.scala | 2 ++ 2 files changed, 3 insertions(+) (limited to 'test/files/run') diff --git a/test/files/run/t6111.check b/test/files/run/t6111.check index 7fd2e33526..1f23a87f73 100644 --- a/test/files/run/t6111.check +++ b/test/files/run/t6111.check @@ -1,2 +1,3 @@ +warning: there were 2 deprecation warning(s); re-run with -deprecation for details (8,8) (x,x) diff --git a/test/files/run/t6111.scala b/test/files/run/t6111.scala index 7cceea1d09..c0bcf17a07 100644 --- a/test/files/run/t6111.scala +++ b/test/files/run/t6111.scala @@ -1,3 +1,5 @@ +// SI-6675 DEPRECATED AUTO-TUPLING BECAUSE BAD IDEA -- MEAMAXIMACULPA +// TODO: remove this test case in 2.12, when the deprecation will go into effect and this will no longer compile // slightly overkill, but a good test case for implicit resolution in extractor calls, // along with the real fix: an extractor pattern with 1 sub-pattern should type check for all extractors // that return Option[T], whatever T (even if it's a tuple) -- cgit v1.2.3