GitLab

[ci skip]

[ci skip]

[ci skip]

Initial feature add: create both Library and Executable on cabal init

Modify replacement properties of `encodeStringUtf8`/`decodeStringUtf8`

[ci skip]

Do not create folders when failing on no .project or .cabal file

This changes `decodeStringUtf8` to not replace U+FFFE and U+FFFF into
U+FFFD, while `encodeStringUtf8` now replaces surrogate pairs
(i.e. code-points U+D800 through U+DFFF which are invalid in UTF-8)
with U+FFFD.

Consequently, `decodeStringUtf8 . encodeStringUtf8` can now properly
round-trip all scalar code-points
(i.e. [U+0000..U+D7FF] ∪ [U+E000..U+10FFFF]).

This should finally address #4644

Restore a few integration test comments and new-build package arguments.

#4909 changed the cabal-version of the package under test, so this commit
adjusts the versions of the Cabal libraries in the test to be consistent with
the cabal-version.

Some comments were lost in the migration to the new integration test suite.

Don't pass `other-modules` to stub executable for detailed-0.9

The stub executable is linked against the test-library
which already contains all `other-modules`, so we need
to remove those from the stub-exe's build-info to avoid
build errors due to duplication.

This addresses #4918

D.S.Program.Hpc: Use relative .mix search paths

Turn gen-extra-source-files into proper package

Prior to GHC 8.0, hpc requires relative search paths. We now pass relative paths
in all cases; we do not want to separately condition on GHC and HPC versions.

Have the solver reject packages with a too-new/unsupported spec-version

Relax bounds for aeson and optparse-applicative in test-suite

Since we now reject unknown spec-versions in the solver, these test-cases
were broken; this replaces the 2 occurences by `cabal-version: 2.0` instead.

(cherry picked from commit 45c102d7)

This compares the request spec-version to the lib:Cabal's version in order to
determine whether cabal is able to properly understand the package. If it's
newer than the currently linked lib:Cabal version it's turned into a global
`FailResult` which the solver treats as desired in terms of backtracking and
error reporting.

This is related to the new spec-version forward-compat scheme (see #4899).

This is a forward-port of #4907 to the `master` branch

Split sections support

Solver: Enforce dependencies on executables (fixes #4781).

Add --enable-split-sections flag and pipe it through to the GHC backend. Note
that some of the implementation here could be made a bit more precise:
-split-sections and -split-objs are mutually exlusive yet the types don't
currently reflect this.

Fixes #4819.

Examples which used the ancient spec-version v1.2 have been updated to
use at least v1.8; and use CPP-Options instead of GHC-Options where
`cabal check` would have warned; avoid automatic flags for features;
also be explicit about the `build-type:` to avoid the implicit `Custom`
default (TODO: we should really change the default with a future
spec-version to `Simple`)

[skip ci]

Change order of hsLibraries