You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering this strange behaviour while executing sbt unidoc in a module of my project which has got simple ADTs and only com.typesafe.scala-logging" %% "scala-logging" % "3.7.2 as a dependency.
[error]
[error] last tree to typer: Ident(op)
[error] symbol: value op (flags: <triedcooking>)
[error] symbol definition: val op: String
[error] tpe: String
[error] symbol owners: value op -> method filterToExpression -> class SelectSQLStatement -> package statement
[error] context owners: method filterToExpression -> class SelectSQLStatement -> package statement
[error]
[error] == Enclosing template or block ==
[error]
[error] Block(
[error] Apply(
[error] "logger"."warn"
[error] // 2 arguments
[error] "Ignored filter with invalid operator: {}"
[error] "op" // val op: String, tree.tpe=String
[error] )
[error] "None"
[error] )
[error]
[error] == Expanded type of tree ==
[error]
[error] TypeRef(
[error] TypeSymbol(
[error] final class String extends Serializable with Comparable[String] with CharSequence
[error]
[error] )
[error] )
[error]
[error] uncaught exception during compilation: scala.MatchError
Honestly, I have no clue of what can cause such a low level exception.
Any hint or suggestion is much apprecciated.
Thanks for the support,
Saverio
The text was updated successfully, but these errors were encountered:
saveveltri
changed the title
Weird Compilation Error while generating class with scala-logging
Weird Compilation Error while generating docs for class with scala-logging
Mar 20, 2018
Hello,
I'm encountering this strange behaviour while executing
sbt unidoc
in a module of my project which has got simple ADTs and onlycom.typesafe.scala-logging" %% "scala-logging" % "3.7.2
as a dependency.Here is an example
scala version is
2.12.4
The exception got is
Honestly, I have no clue of what can cause such a low level exception.
Any hint or suggestion is much apprecciated.
Thanks for the support,
Saverio
The text was updated successfully, but these errors were encountered: