Daniel Urban
Daniel Urban
I guess the reason could be, that during compilation, WartRemover might run after the "patmat" phase (it's only specified that it should run after the "typer" here: https://github.com/puffnfresh/wartremover/blob/85719aaf9f7e29a8874a97d946f6cd33bad3d117/core/src/main/scala/wartremover/Plugin.scala#L54). While WartTestTraverser...
scalastyle-sbt-plugin 0.7.0 Scalastyle 0.7.0 Scala 2.11.7
Update: I tried with Scalastyle 0.8.0, and I got the same error.
I don't know, what's in the linked discussion (I can't read it), but I don't think this is correct. Not having a finalizer doesn't make the effect uncancellable: the `case...
I think this is related to this comment on `Resource#start`: ``` * 4. If the fiber succeeds and .cancel lost the race or wasn't called, * finalize naturally when the...
See #2963, which fixes this specific case. However, it is still possible to do a start/join and observe a similar reporting of an error.
I think it's just a race between the started fiber and `join`. If we do this: ```scala for { fiber
@boggle Thanks, I'll take a look.
Well ... documenting it and doing nothing is definitely an option. I don't think it's a very good one, because: - The consequences of the lack of opacity are very...
@TimWSpence I'm talking about the fact, that while we have the invariant that `r1 < r2` (and when writing, we uphold this invariant), we still can observe a case in...