New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-deterministic errors reported when implicit parameters are involved #4539
Comments
Imported From: https://issues.scala-lang.org/browse/SI-4539?orig=1 |
@adriaanm said: Maybe it's caches filling up, or other limits being reached, but I find it hard to believe it's just a matter of using the compiler daemon at certain time intervals. Are you sure your classpath was the same (with the same contents) everytime? Maybe you had some stale classfiles laying around? Can you try with fsc as well (I sure hope this can't be reproduced with scalac!). There must be a deterministic way to trigger both results; lacking that, I'm afraid it's going to be nearly impossible to fix. (I did try to repro, will try again in an hour...) |
@gkossakowski said: I fully understand that there's no chance to fix this (potential) bug until it can be reproduced reliably. Actually, what's odd started to get the same results for all runs of scalac for all versions. I always get two errors demonstrated above. What about you? Are you getting two errors, two? Discussion on mailing list with Johannes suggests that he was getting one error for my code too so there's some independent confirmation. Anyway, I'll try to spend a little bit more time on this on a weekend and see if I can provide some more details. |
@paulp said: |
=== What steps will reproduce the problem (please be specific and use wikiformatting)? ===
=== What is the expected behavior? ===
I'm not sure if this code should compile at all but what I would expect is deterministic result (code compiles or compiler fails with the same sort of problems reported).
=== What do you see instead? ===
Either:
or:
I couldn't find any way to reliably trigger first or second behaviour. The only thing that seems to be consistent is that scalac tends to 'stick' to one of behaviour for a while so if you want to reproduce it you might want to have one hour between subsequent runs of scalac.
=== Additional information ===
https://groups.google.com/group/scala-user/browse_thread/thread/f83055972c91a514
=== What versions of the following are you using? ===
The text was updated successfully, but these errors were encountered: