-
I don't fully understand the nuances, but in several places in Distribution.Cabal.Simple.GHC[(JS)] the extensions specified in a cabal file are checked for TemplateHaskell, and if it is present then o…
-
I've removed token quaisiquotes from public API, because we don't have anyone using them except for https://github.com/Duhemm/parsermacros and our internal prettyprinters. In the future we may find it…
-
```
val q"($q, y: Y, ..$e)" = q"(x: X, y: Y, z: Z)"
q: scala.meta.Term.Param = x: X
e: scala.collection.immutable.Seq[scala.meta.Term.Param] = List(y: Y, z: Z)
```
Here `e` should have been `List(z: …
Dveim updated
7 years ago
-
Use some form of read parsing instead of relying on the reader macros. This will free up the ```@``` and ```,``` symbols for binding to other forms (for example, ```@``` should become matrix-multiply)
-
Here's program that works with `persistent-2.5` and `persistent-sqlite-2.6` but doesn't work with `persistent-2.7.1` and `persistent-sqlite-2.6.3`:
```haskell
{-# LANGUAGE ConstraintKinds …
-
This could help with compilation times but we need to validate this hypothesis.
-
Current implementation of quasiquotes (described in detail in https://github.com/scalameta/scalameta/issues/157) relies on `materializeAst` to [reify](https://github.com/scalameta/scalameta/blob/8b71a…
-
```
[info] ! liftable.lift tuple: Exception raised on property evaluation.
[info] > Exception: java.lang.IllegalArgumentException: requirement failed: Tuples with 16 arity aren't supported
```
h…
-
Rationale: One cannot write a portable library to implement syntax parameters so support by the core system is needed.
-
```
scala> val paramss = List(List(param"x: Int"))
paramss: List[List[meta.Term.Param]] = List(List(x: Int))
scala> q"def foo(...$paramss)(x: Int) = ???"
:31: error: Implementation restriction: can't…