haskell / haskell/cabal

`cabal check` should recommend against using the `stability` field

Open
#4,290 3 comments 1 reaction 0 assignees View on GitHub
cabal-install: cmd/check type: enhancement
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

It seems to be consensus that the `stability` field is often misleading and shouldn't be used any more. See for example [Simon Marlow's comment on this issue](http://stackoverflow.com/a/3847493/1013393).

Therefore I propose that `cabal check` should discourage any explicit settings in the `stability` field.

As the `stability` field can also be set on a per-module basis (see e.g. [Data.Set](http://hackage.haskell.org/package/containers-0.5.9.1/docs/Data-Set.html)), I'd like `cabal check` to check all the modules too. My questions are:

1. Is checking the modules within the scope of `cabal check`?
2. Is the machinery for checking modules already in place?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.