I wonder if there is a good reason for this optical mismatch between e. d. pattern matching that uses simple
case foo =>
so that there is no action.
It would be wise to have something like
import foo.bar.{Baz => }
instead
import foo.bar.{Baz => _}
considering what is _used as βimport everythingβ into the same statement?
_
I would suggest it for symmetry with renamed imports:
import java.util.{Collection => JCollection, _}
If we want to import an invalid identifier:
import java.util.{Collection => _ , _}
( , _ , => , .)
=>
Source: https://habr.com/ru/post/1746870/More articles:Eclipse Java plugin development - programmatically save all project files - javawriting XML using Xerces 3.0.1 and C ++ on windows - c ++Exception in the Xerces two-line program - c ++Best practice for creating an auxiliary method of a business object - memory-managementDifference between document classes - javaAssert.AreEqual () exception in VS2010 - .netTruncating a base table in a view - sql-server-2008Is rand () predictable in C ++ - c ++best approach to validating jsf form - jsfProper use of s / rand or Boost :: random - c ++All Articles