Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by ValentinRutz
, 1 year ago
encountered unexpected trees during syntactic + semantic merge: Term.ApplyInfix(Lit.Int(0), Term.Name("+"), Nil, Seq(Lit.Int(2))) Lit.Int(2) <-(Term.ApplyInfix) 0 + 2 ->(Lit.Int) 2
via GitHub by ValentinRutz
, 1 year ago
encountered unexpected trees during syntactic + semantic merge: Term.ApplyInfix(Lit(3), Term.Name("::"), Nil, Seq(Term.Name("x"))) Term.Block(Seq(Defn.Val(Nil, Seq(Pat.Var.Term(Term.Name("x$1"))), Some(Type.Name("Int")), Lit(3)), Term.Apply
scala.meta.internal.ast.MergeException: encountered unexpected trees during syntactic + semantic merge:
 Term.ApplyInfix(Lit.Int(0), Term.Name("+"), Nil, Seq(Lit.Int(2)))
 Lit.Int(2)
 <-(Term.ApplyInfix) 0 + 2
 ->(Lit.Int) 2	at scala.meta.internal.ast.mergeTrees$.fail(MergeTrees.scala:281)	at scala.meta.internal.ast.mergeTrees$.scala$meta$internal$ast$mergeTrees$$failCorrelate(MergeTrees.scala:246)	at scala.meta.internal.ast.mergeTrees$loop$2$.apply(MergeTrees.scala:175)	at scala.meta.internal.ast.mergeTrees$.apply(MergeTrees.scala:220)	at scala.meta.internal.hosts.scalac.contexts.Adapter.loop$1(Adapter.scala:118)	at scala.meta.internal.hosts.scalac.contexts.Adapter.loop$1(Adapter.scala:88)	at scala.meta.internal.hosts.scalac.contexts.Adapter.typecheck(Adapter.scala:121)	at scala.meta.internal.hosts.scalac.contexts.Adapter.defns(Adapter.scala:125)	at scala.meta.semantic.Api$XtensionSemanticRefDefn.defns(Api.scala:137)	at scala.meta.semantic.Api$XtensionSemanticRefDefn.defn(Api.scala:139)