Skip to content

Lots of ambiguous type errors when using OverloadedStrings #120

Open
@tysonzero

Description

It seems like the trend is increasingly towards enabling OverloadedStrings for most projects, given the inferiority of String for most tasks.

Currently this leads to a ton of ambiguity errors when using various functions from Language.Javascript.JSaddle, and they are quite verbose to fix.

Is there any interest in exporting variants that aren't polymorphic in the string-y argument?

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