meta-ticket: Quasiquotes are no longer being improved

[SethTisue]

pull requests against quasiquote support (which has always been experimental) in scala.reflect will certainly be considered, but it's now been a long time since anyone has touched it. rather than leave a bunch of tickets open on it, let's just have this one

[SethTisue]

closed the following quasiquotes tickets:

• Quasiquote splicing for empty lists misbehaves during trait instantiation #7945
• Creation of names prefixed with other names isn't straightforward in quasiquotes #8078
• Make extraction of repetitive code patterns easier in quasiquotes #8164
• There is no easy way to position nested trees in a quasiquote #8250
• There is no easy way to extract types from nested trees in quasiquote #8257
• reify shouldn't unexpand macros #6115
• Macro expansion throws a RuntimeException during the tail call elimination phase #7829
• Quasiquotes fail to match a typechecked case class #8312
• Quasiquotes fail to match class modifiers inside block #8313
• Can't match classOf after typechecking with quasiquotes #8384
• q"trait X" doesn't match q"trait X{}" #8396
• Trait pattern quasiquote might not match interface traits without mods #8399
• Consider different syntax alternatives for quasiquotes #8401
• QQ crash extracting nested xml #8436
• Quasiquotes bottom type check is too restrictive #8452
• Allow unquoting names as function expression arguments #8455
• Quasiquotes can't parse mods on first member in template body #8458
• Persist comments in trees generated by quasiquotes #8470
• weird syntax necessary to write a lambda quasiquote #8480
• can't splice names into lambda parameters #8481
• names don't get converted to binds when spliced into patterns #8482
• weird trees are created when an ident is spliced into a function parameter's name #8770
• regression in ClassDef quasiquotes in 2.11.2 under -Yrangepos #8771
• StackOverflow in importers when a symbol has an existential info #8833
• Unquoting of options with ..$ produces unexpected results #8972
• extra () in Tree causing pain #9320
• Strange inliner behavior after upgrading to 2.11.7 #9372
• Quasiquotes do not pattern match Java static method #9404
• Anonymous class creation with empty body list in quasiquotes #10691
• Scala 2.11.12 quasi-quote interpolation "losing" trees in nested macros invocations #10745

[SethTisue]

this has caused some angst on Gitter and Reddit. some clarifications:

• pull requests on quasiquotes will still be considered
• does this reflect a change in the maintenance/support status of quasiquotes/macros/reflect?
  • no. this is just backlog grooming, trying to not have so many stale tickets that nobody has looked at in years
• why only close quasiquote tickets, not all macros/reflect tickets?
  • I singled out the quasiquotes tickets mainly because Denys used the issue tracker to record a lot of jottings and ideas, including vague future plans, so the average current relevance of the tickets was low. I'm also closing many stale macros and reflect tickets, just a bit more selectively. feel free to reopen, or suggest a reopen, on any individual ticket where you feel I was too hasty
• does this affect Lightbend support customers?
  • no. macros are experimental, always have been, and therefore aren't officially covered by Lightbend support. as our customers know, we always do our best, regardless, to help with support tickets in this area, within reason. whether some tickets are open or closed doesn't represent any change to that. support customers can always ask us anything