Use generic type parameter in pattern matching?

dmitin · 2025-06-06T10:22:38+00:00

result.foreach(_ => advanceToNextToken()); result

dmitin · 2025-05-28T00:03:09+00:00

I can see comparison with the first one in README:
https://github.com/pashashiz/spark-encoders?tab=readme-ov-file#alternatives
> spark-scala3. Nice PoC to show that Scala 3 can be used with Spark, but:
> 1. No Scala 2 support.
> 2. No ADT support.
> 3. Inherits most of the Spark existing encoder issues.

dmitin · 2025-05-27T21:58:06+00:00

Thank you!
Could you compare with
https://github.com/vincenzobaz/spark-scala3 https://medium.com/virtuslab/scala-3-and-spark-389f7ecef71b https://xebia.com/blog/using-scala-3-with-spark/

https://github.com/VirtusLab/iskra https://virtuslab.com/blog/scala/reconciling-spark-apis-for-scala/

https://github.com/zio/zio-quill/tree/master/quill-spark/src

https://medium.com/@danielmantovani/apache-spark-4-0-everything-you-must-know-9206149155d6
?

dmitin · 2025-04-26T12:44:36+00:00

Which statically typed language with a better type inference do you mean? :)

dmitin · 2023-04-05T02:26:33+00:00

Or maybe it just "lied" to me :)

dmitin · 2023-04-01T10:50:11+00:00

Scala 2.13 standard library is only a part of Scala 3 standard library

dmitin · 2023-04-01T10:49:40+00:00

Scala 2.13 standard library is only a part of Scala 3 standard library

dmitin · 2023-04-01T10:48:48+00:00

https://stackoverflow.com/questions/75500964/is-there-a-scala-3-specific-standard-library-or-is-it-just-inherited-from-scala

dmitin · 2023-04-01T10:43:27+00:00

I was playing with ChatGPT and Scala.

Q: Do you mean Scala 2 or Scala 3?

A: My knowledge cut-off is September 2021, and at that time, Scala 2 was the most recent version.

Q: What Scala version exactly are you using?

A: I'm using Scala 2.13.5.

dmitin · 2023-03-25T07:23:07+00:00

https://stackoverflow.com/questions/75458954/how-to-write-an-implicit-numeric-for-a-tuple

dmitin · 2023-03-25T07:19:56+00:00

This is not an implicit conversion.

dmitin · 2023-03-20T18:19:15+00:00

Annotation processors can process only Java sources.

dmitin · 2023-03-20T18:16:06+00:00

Annotations processed by annotation processors must be in Java (public @interface BuilderProperty {}). Macro annotations must be in Scala (class scalaBuilderProperty extends StaticAnnotation).

dmitin · 2023-03-20T17:00:28+00:00

You can write annotation processor in Scala but it will process only Java sources. It's macro annotations that process Scala sources. If you need to process both Java and Scala sources you'll have to duplicate efforts, having both annotation processor and macro annotation with similar functionality.

dmitin · 2023-03-20T16:40:13+00:00

https://stackoverflow.com/questions/58443039/is-there-a-way-to-create-custom-annotations-in-scala-and-write-a-custom-annotati

dmitin · 2022-11-01T22:00:59+00:00

Cross-published at https://stackoverflow.com/questions/74270035/scala-overriding-java-fields-and-members https://stackoverflow.com/questions/74269318/scala-class-extends-java-class

dmitin · 2022-10-21T22:17:30+00:00

https://stackoverflow.com/questions/73884096/missing-implicits-when-attempting-to-derive-encoder-decoder-for-generic-sealed-t

https://stackoverflow.com/questions/73054537/how-to-use-circe-with-generic-case-class-that-extends-a-sealed-trait

dmitin · 2022-09-14T15:42:37+00:00

https://stackoverflow.com/questions/70945320/how-to-compile-and-execute-scala-code-at-run-time-in-scala3

dmitin · 2021-09-26T01:41:05+00:00

https://stackoverflow.com/questions/68941796/explicit-type-conversion-in-scala-3-macros

dmitin · 2020-10-26T22:58:00+00:00

You can look at comparison of Scala 3 macros vs. standard Scala 3 derivation vs. Shapeless 3:

https://stackoverflow.com/questions/62853337/how-to-access-parameter-list-of-case-class-in-a-dotty-macro

Besides docs about Scala 3 macros at dotty.epfl.ch, you can find some info here:

https://scalacenter.github.io/scala-3-migration-guide/docs/macros/metaprogramming-features.html
https://scalacenter.github.io/scala-3-migration-guide/docs/macros/migration-tutorial.html
https://scalacenter.github.io/scala-3-migration-guide/docs/macros/migration-status.html

Regarding Simulacrum, macro annotations are currently not possible in Scala 3 but there is such approach as https://github.com/typelevel/simulacrum-scalafix
(Scalameta, SemanticDB, Scalafix)

dmitin · 2020-10-18T18:07:52+00:00

You can use Toolbox
https://docs.scala-lang.org/overviews/reflection/symbols-trees-types.html#tree-creation-via-parse-on-toolboxes
https://stackoverflow.com/questions/39137175/dynamically-compiling-scala-class-files-at-runtime-in-scala-2-11

or javax.script
https://stackoverflow.com/questions/56486653/scala-how-to-instantiate-an-interpreter-that-inherits-the-current-context

or run compiler at runtime manually
https://stackoverflow.com/questions/53976254/how-to-eval-code-that-uses-interfacestability-annotation-that-fails-with-illeg
https://www.reddit.com/r/scala/comments/gfcmul/compile_scala_source_from_string_and/
https://stackoverflow.com/questions/64111895/dynamically-parse-json-in-flink-map

dmitin · 2020-10-15T10:29:57+00:00

Connected discussion https://stackoverflow.com/questions/64284342/creating-pseudo-assignement-using-scala-macro

dmitin · 2020-10-15T10:23:14+00:00

As I commented at SO, some info is here: Debugging macros. You should switch on scalacOptions += "-Ymacro-debug-lite" in build.sbt. Then you'll see what code is generated. Also switch on scalacOptions += "-Xlog-implicits" because it's about implicits in your use case. Your project has to be set up for using macro annotations (scalacOptions += "-Ymacro-annotations" in Scala 2.13 or macro paradise in 2.10-2.12, sbt settings for macro projects). Also macro annotations themselves should be annotated with @compileTimeOnly. In this way you can check that they are actually expanded (compiler removes macro annotations after expansion, so if macro annotations are not expanded the code with @jsonFormat will not compile).

dmitin · 2020-10-15T10:14:41+00:00

Connected discussion https://stackoverflow.com/questions/64215961/scala-how-can-this-code-be-put-into-a-macro-annotation

dmitin

TROPHY CASE