Closed He-Pin closed 4 months ago
@fanf Would you like to give this a try? I mean locally.
The PR looks good to me, once you get CI green I can merge it and close out the bounty
@lihaoyi Would you like give it another round of run, thanks.
@lihaoyi The CI is happy now:)
Note: in Scala 2.12, I added two mina filters where the nowarn is the scala nowarn now.
@He-Pin can we leave the original nowarn
in place but deprecated? That way we can avoid adding the mima filters
@lihaoyi OK, I think that would be better.
@lihaoyi I have updated and removed the added mima.
@He-Pin not sure if I'm missing something, but where is the new version of ScalacParser used in the PR?
@lihaoyi Because I updated the Scala 2.13.x to 2.13.14 in this PR, and with https://github.com/scala/scala/pull/10406 , the additional actions: List[CodeAction]
parameter is added, so when do cross compiling with Scala 2.12 and Scala 2.13, it will raise an error override nothing
without this change in the scalaparse tests.
@He-Pin got it, looks good! Can send me details at haoyi.sg@gmail.com and I'll close out the bounty
thanks, I just implement a jsonpath (https://www.rfc-editor.org/rfc/rfc9535#name-collected-abnf-grammars) with Fastparse at work, it works great.
Motivation: refs: https://github.com/com-lihaoyi/fastparse/issues/285 with reading: https://www.scala-lang.org/2021/01/12/configuring-and-suppressing-warnings.html
Modification:
-Xlint:unused
to reproduce the problem3
is enabled.@nowarn
annotation directly.WhiteSpace
macroResult: I think the issue is fixed now, and as I'm using Fastparse within a Java project, so I was not knowing this issue. All tests passed locally.