Implicit parameters at the same scope in other files

Question

Reviewing implicit parameters (and conversions) precedence rules at http://docs.scala-lang.org/tutorials/FAQ/finding-implicits.html I found the following priority list:

First look in current scope

Implicits defined in current scope

Explicit imports

wildcard imports

~~Same scope in other files~~

...

I wonder why Same scope in other files is crossed out. Is it a pending to implement feature? Has it been removed for some reason? My so far experience shows that the feature isn't available but I'd like to know why is it listed.

score 1 · Answer 1 · answered Mar 17 '15 at 17:27

1

If you look below, you can see:

Same Scope in Other Files Edit: It seems this does not have a different precedence. If you have some example that demonstrates a precedence distinction, please make a comment. Otherwise, don’t rely on this one. This is like the first example, but assuming the implicit definition is in a different file than its usage. See also how package objects might be used in to bring in implicits.

answered Mar 17 '15 at 17:27

skozlov

384
1
12

It might be due my limited English skills but I don't find that comment conclusive: *...Otherwise, don’t rely on this one...* Could you provide more detail? As far as I understand, there is some uncertainty around the feature but I may be wrong. – Pablo Francisco Pérez Hidalgo Mar 17 '15 at 17:34
1

@PabloFranciscoPérezHidalgo It was always crossed out. That content was originally posted in [this answer](http://stackoverflow.com/a/5598107/2292812). – Michael Zajac Mar 17 '15 at 18:20
@m-z Thanks, Do you have any clue on the future availability of the feature? – Pablo Francisco Pérez Hidalgo Mar 17 '15 at 18:22
@PabloFranciscoPérezHidalgo No, I think it was just there and crossed out in the SO post. – Michael Zajac Mar 17 '15 at 18:27

Implicit parameters at the same scope in other files

1 Answers1