Skip to content

network-3.1.2.0 uses TypeApplications, which makes it fail to compile with GHCs pre-8. #475

Description

@phadej

Please add

other-extensions: TypeApplications

to cabal file or remove use of TypeApplications.

Activity

  1. added 2 commits that reference this issue on Aug 10, 2020
    e3845a9
    af9afaa
  2. kazu-yamamoto commented on Aug 12, 2020

    @kazu-yamamoto
    Collaborator

    I don't understand why other-extensions: is necessary. We don't support GHC 7.x anymore.

  3. RyanGlScott commented on Aug 14, 2020

    @RyanGlScott
    Member

    I've run into this issue as well. To be clear, this results in failing build plans involving network-3.1.2.0 on GHC 7.10.3 and 7.8.4. An example of this breaking a CI build can be found here:

    Network/Socket/Posix/Cmsg.hsc:7:14:
        Unsupported extension: TypeApplications
    

    I don't understand why other-extensions: is necessary. We don't support GHC 7.x anymore.

    The issue is that network-3.1.2.0 happily allows build plans with GHC 7.8.4 and 7.10.3 due to the lower bounds on base (>= 4.7). It looks like this has been changed in master, but these changes have not yet made it to Hackage (e.g., with a revision).

    Regarding other-extensions, it's another piece of information that cabal's constraint solver uses when constructing build plans. If you state other-extensions: TypeApplications, then cabal will rule out any build plans involving compilers that do not support the TypeApplications extension (such as 7.8 and 7.10).

  4. kazu-yamamoto commented on Aug 18, 2020

    @kazu-yamamoto
    Collaborator

    #473 has been already merged. Is that good enough?

  5. RyanGlScott commented on Aug 18, 2020

    @RyanGlScott
    Member

    It would be good enough for me, at least. However, those changes are not yet on Hackage, so as things currently stand, network-3.1.2.0 is still broken for me on 7.8 and 7.10.

  6. kazu-yamamoto commented on Aug 18, 2020

    @kazu-yamamoto
    Collaborator

    I have modified the metadata on hackage. Now resolved?

  7. RyanGlScott commented on Aug 18, 2020

    @RyanGlScott
    Member

    That resolved my issues, yes. Many thanks!

  8. kazu-yamamoto commented on Aug 18, 2020

    @kazu-yamamoto
    Collaborator

    OK. Let's close. Thank you for letting us know this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions