scalameta doesnt have anything to do with macros anymore
Hi, I am a bit puzzled: I tried the example from the docs about parsing the simple "a + b".
import $ivy.`org.scalameta::scalameta:4.3.21`
import scala.meta._
println("a + b".parse[Stat].get.structure)Unfortunately I get an error that is not very helpful
java.lang.NoSuchMethodError: scala.meta.Dialect.allowEndMarker()Z
scala.meta.internal.parsers.ScalametaParser$EndMarkerIntro$.unapply(ScalametaParser.scala:607)
scala.meta.internal.parsers.ScalametaParser$$anonfun$3.applyOrElse(ScalametaParser.scala:3907)
scala.meta.internal.parsers.ScalametaParser$$anonfun$3.applyOrElse(ScalametaParser.scala:3902)
scala.PartialFunction$Lifted.apply(PartialFunction.scala:310)
...What do I do wrong? I use Ammonite 2.2.0 and Scala 2.13.3 (under Java 9). Thanks!
might be wrong, but I don't see what could cause it, that method should be available
Very strange: I tried exactly the same code on another machine (Linux as opposed to my main Mac). As expected it loads quite a few jars on the first run.
Loading...
Welcome to the Ammonite Repl 2.1.4 (Scala 2.13.2 Java 11.0.7)
@ import $ivy.`org.scalameta::scalameta:4.3.21`
https://repo1.maven.org/maven2/org/scalameta/scalameta_2.13/4.3.21/scalameta_2.13-4.3.21.pom
100.0% [##########] 3.1 KiB (1.4 KiB / s)
...But the snippet then produces a very similar error:
@ println("a + b".parse[Stat].get.structure)
java.lang.NoSuchMethodError: 'boolean scala.meta.Dialect.allowEndMarker()'
scala.meta.internal.parsers.ScalametaParser$EndMarkerIntro$.unapply(ScalametaParser.scala:607)
scala.meta.internal.parsers.ScalametaParser$$anonfun$3.applyOrElse(ScalametaParser.scala:3907)
scala.meta.internal.parsers.ScalametaParser$$anonfun$3.applyOrElse(ScalametaParser.scala:3902)
scala.PartialFunction$Lifted.apply(PartialFunction.scala:310)
scala.PartialFunction$Lifted.apply(PartialFunction.scala:306)
scala.meta.internal.parsers.ScalametaParser.entrypointStat(ScalametaParser.scala:3938)
scala.meta.internal.parsers.ScalametaParser.$anonfun$parseStat$2(ScalametaParser.scala:59)
scala.meta.internal.parsers.ScalametaParser.parseRule(ScalametaParser.scala:48)
scala.meta.internal.parsers.ScalametaParser.parseStat(ScalametaParser.scala:59)
scala.meta.parsers.Parse$.$anonfun$parseStat$1(Parse.scala:14)
scala.meta.internal.parsers.ScalametaParser$$anon$214.apply(ScalametaParser.scala:4190)
scala.meta.parsers.Api$XtensionParseDialectInput.parse(Api.scala:25)
scala.meta.parsers.Api$XtensionParseInputLike.parse(Api.scala:14)
ammonite.$sess.cmd2$.<clinit>(cmd2.sc:1)I can send the log of all jars that have been pulled the first time.
Hi! Given:
def mkParam(p: Param): Term.Param = q"${p.value}: String"and
for {
…
params = matched.params.map(mkParam)
} yield q"def $name($params): Response = client.$method($path)"I run into two issues:
error: type mismatch;
found : meta.Term.Ascribe
required: scala.meta.Term.Param
def mkParam(p: Param): Term.Param = q"${p.value}: String"
^and
error: type mismatch when unquoting;
found : List[scala.meta.Term.Param]
required: scala.meta.Term.Param
} yield q"def $name($params): Response = client.$method($path)"
^I did not find documentation about how to construct interpolated quasi quote strings to create parameter lists for def and how to create Parameters in general. How do I do this and/or where in the documentation is this?
what happens if you do
param"${p.value}: String" instead of q"${p.value}: String"?
thanks! That leaves me with the other problem, still
error: type mismatch when unquoting;
found : List[scala.meta.Term.Param]
required: scala.meta.Term.Param
} yield q"def $name($params): Response = client.$method($path)"
^
@ val params = List(param"a: Int", param"b: String")
params: List[Term.Param] = List(
Term.Param(List(), Term.Name("a"), Some(Type.Name("Int")), None),
Term.Param(List(), Term.Name("b"), Some(Type.Name("String")), None)
)
@ q"def foo(..$params) = a".syntax
res7: String = "def foo(a: Int, b: String) = a"
add
.. before $params
Those references are quite dense
ah, yes, I see it now. Thanks again! Seems that the documentation was meant to be read slightly different than how I browsed it
OK, so, how do I construct a
Term.Name using string interpolation? When I do this, all I get is a Stat
method: Term.Name = q"${someString.toLowerCase}" is what I do
I also, in my neverending wisdom, tried adding <>:
error: type mismatch when unquoting;
found : String
required: scala.meta.Term.Name
method: Term.Name = q"<${someString.toLowerCase}>"to no avail.
error: type mismatch;
found : scala.meta.Stat
required: scala.meta.Term.Name
method: Term.Name = q"${someString.toLowerCase}"
oh, I see it now. The example doesn't actually have a
$ sign. Oh my
Guess I have to create them manually
There are some cases where you can interpolate a string and it's interpreted as a term name
but it's usually simplest to use
Term.Name(String) if you know you need a term name
I gotta say scalameta is really cool and it's fun to use :)
q"a" becomes Term.Name("a")
I added a note in the quasiquote spec about using
Term.Name when interpolation is needed scalameta/scalameta@4e5dabd
@urbanchr the issue appears to be caused by this line in Ammonite where it adds scalameta 4.3.20 to the classpath by default https://github.com/lihaoyi/Ammonite/blob/master/build.sc#L205