As others have mentioned, it's an import rename. There is however one further feature that proves astoundingly-useful on occasion that I would like to highlight: If you "rename" to _, the symbol is no longer imported.

This is useful in a few cases. The simplest is that you'd like to do a wildcard import from two packages, but there's a name that's defined in both and you're only interested in one of them:

import java.io.{ File=>_, _ }
import somelibrary._

Now when you reference File, it will unambiguously use the somelibrary.File without having to fully-qualify it.

In that case, you could have also renamed java.io.File to another name to get it out of the way, but sometimes you really do not want a name visible at all. This is the case for packages that contain implicits. If you do not want a particular implicit conversion (e.g. if you'd rather have a compile error) then you have to delete its name completely:

import somelibrary.{RichFile => _, _}
// Files now won't become surprise RichFiles

参考链接:

https://stackoverflow.com/questions/31652959/what-does-mean-in-import-in-scala

相关文章:

  • 2021-10-30
  • 2021-08-29
  • 2021-12-25
  • 2021-11-11
  • 2022-01-12
  • 2021-10-17
  • 2021-11-16
  • 2021-12-28
猜你喜欢
  • 2021-06-19
  • 2022-12-23
  • 2021-09-27
  • 2021-07-17
  • 2022-12-23
  • 2022-12-23
  • 2021-07-20
相关资源
相似解决方案