Add `runhaskell Setup.hs` command corresponding to `cabal check`?

[mpilgrem]

Describe the feature request
Is there any appetite within the Cabal project to add a runhaskell Setup.hs command that corresponds to cabal check?

It seems to me that a runhaskell Setup.hs check could go hand-in-hand with the existing runhaskell Setup.hs sdist.

Additional context
EDIT: I've since realised that what Stack does (the text below) is not a good motivation for the above. However, perhaps it has merit on its own terms, so I have not closed the issue.

The motivation is that Stack makes use of module Distribution.PackageDescription.Check. However, because there is no runhaskell Setup.hs command that corresponds to cabal check, Stack uses the version of the Cabal package that Stack is built against - which could be older than the version of the Cabal package that a Stack user is building with.~

(I appreciate that Stack could build another small executable to make use of the 'checking' functionality provided by Cabal (the library), but it would be nice if the Setup executable had 'checking' within its scope.)

[ffaf1]

Stack uses the version of the Cabal package that Stack is built against - which could be older than the version of the Cabal package that a Stack user is building with.

Sorry I am lost on this one. stack is build against a specific version of Cabal, that maskes sense and I understand. What does “than the version of the Cabal package that a Stack user is building with” refer to?

[mpilgrem]

@ffaf1, Stack follows the original Cabal specification and accesses the Cabal 'simple' build infrastructure through an executable compiled from a package's Setup.hs. That 'Setup' executable is often built against a different version of Cabal than Stack itself is built against - normally, by default, the Cabal boot package for the version of GHC that the Stack user has specified.

EDIT1: To make that concrete, Stack 3.1.1 is built against Cabal-3.10.3.0. However, if a Stack user has specified GHC 8.4.1, which shipped with Cabal-2.2.0.0, Stack will be building (by default) with that version of Cabal (the library). None of that is problematic. However, if a user of Stack specifies GHC 9.10.1, Stack will be building with Cabal-3.12.0.0 but 'checking' using Cabal-3.10.3.0.

EDIT2: I've realised that what Stack does is not a good motivation and edited my initial post accordingly.