Reconsider failing `.value` inside lambda expression

steps

    test in Test := {
      List(1, 2, 3) foreach { x =>
        streams.value.log.info(s"foo $x")
      }
      (test in Test).value
    }

problem

build.sbt:17: error: The evaluation of `streams` inside an anonymous function is prohibited.

Problem: Task invocations inside anonymous functions are evaluated independently of whether the anonymous function is invoked or not.

Solution:
  1. Make `streams` evaluation explicit outside of the function body if you don't care about its evaluation.
  2. Use a dynamic task to evaluate `streams` and pass that value as a parameter to an anonymous function.

        streams.value.log.info(s"foo $x")
        ^
[error] sbt.compiler.EvalException: Type error in expression
[error] Use 'last' for the full log.

expectation

The task does exactly what I want it to do. It should work without warnings or error.

notes

In general, an error (or even a warning) should be displayed when we are 90% certain that the build is doing something against what the user has intended. In this case, I don’t think it is.

Ref https://github.com/lucidsoftware/neo-sbt-scalafmt/pull/11, https://github.com/sbt/sbt/pull/3216/commits/ca3acc4e52668c77a1f2dfa0cc247a45936cf7bd

/cc @jvican

[dwijnand]

Personally I’d want it to disable all linting, not just for lambdas - also if’s etc:

import sbt.dsl.power

[jrudolph]

IMO the whole linter should be removed not only for this particular case but for the others as well. In the default case the macro expansion does the right thing of evaluating the task every time. I guess that’s somewhat surprising for new users but it’s a consequence of the system (and the same as before with the manual syntax). In the case where you want the dynamic behavior you can still use the `dynamicTask`` workaround.