`template-haskell-depends`
Los mantenedores suelen responder en 3 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- haskell
- Área
- build-system
Línea de trabajo
Start by identifying where Cabal defines, parses, and uses dependency fields such as build-depends, then trace how those fields are merged for builds. The feature is done when a template-haskell-depends field is supported and, as described here, its dependencies are merged with build-depends.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the feature request
There has long been a somewhat folkloric desire to separate out the dependencies which are needed for Template Haskell from those which are compiled and linked against.
Some people have suggested having a field like native-build-depends, but I think there is more appetite for something that is more semantically named, leaving us with some flexibility in exactly how it's used (c.f. plugin-depends).
So I suggest that we add a field template-haskell-depends for dependencies that are needed only for Template Haskell splice code. Many packages would appear in both, if they e.g. provide a splice that generates code containing identifiers from the library, in which case we also need to link against it. But some could be pure splice code.
For now, cabal would have to just merge this with build-depends since I don't think that GHC currently provides a way to take advantage of the additional information.
Additional context
I am working on buck2 support for cabal. Knowing which packages are used in TH is quite helpful, as we need to wait for their shared libraries to be built before we can proceed. At the moment we are probably going to let users specify which of their build dependencies are TH dependencies with a cabal x- extension field, but it would be nice to have a real field!
Other misc benefits:
- A TH-only dependency doesn't have to be built with profiling support (since it won't be run at runtime)
- In principle we could solve for TH-only dependencies separately, since they're not linked in
Non-exhaustive list of previous mentions:
- https://github.com/haskell/cabal/issues/2965#issuecomment-607282235 ("And if template haskell step would ever be separated, then a separate package db & dependencies for that too.")
- https://github.com/haskell/cabal/pull/4104#issuecomment-266838873 ("host-only" dependencies)
- https://ghc-proposals.readthedocs.io/en/latest/proposals/0682-explicit-level-imports.html ("Ultimately, it would make sense to expose this distinction at the level of Cabal packages, so that Cabal could build package dependencies only for the stages at which they are required. This would primarily be of value in cross-compilation scenarios.")
- Lenguaje dominante
- Haskell
- Estrellas
- 1.8k
- Forks
- 766
- Merge medio
- 5 d 21 h
- PR fusionados (30 d)
- 27
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de haskell/cabal
-
needs triage type: enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 3 días
-
needs triage type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
haskell/cabal#12568 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
needs triage type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
haskell/cabal#12525 · 3 comentarios · 1 reacción ·
Los mantenedores suelen responder en 3 días
-
Required version of `cabal-install` to build CabalPosiblemente ocupada @philderbeast la tomó hace 24 días. Abiertodocumentation type: discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
haskell/cabal#12477 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 3 días
-
Document which are our LTS releasesPosiblemente ocupada @KeuqS la tomó hace 41 días. Abiertodocumentation type: discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
haskell/cabal#12373 · 2 comentarios ·
Los mantenedores suelen responder en 3 días
Todos los issues de haskell/cabal
Issues similares
-
bug desktop
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
simplex-chat/simplex-chat#8291 ·
Los mantenedores suelen responder en 1 día
-
[BUG]: C# programs with top-level statements fail to compilePosiblemente ocupada @AsyncNigam la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
compiler-explorer/compiler-explorer#9625 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
reflex-0.10Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
commercialhaskell/stackage#8180 ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
OpenZeppelin/canton-contracts#140 ·
Los mantenedores suelen responder en 1 día
-
takeInterval yields nothing, dropInterval drops nothingPosiblemente ocupada @GuillaumedeVolpiano la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
composewell/streamly#3271 ·