Skip to content

Bad ergonomy with toplevel #58

@gadmm

Description

@gadmm

With Merlin being currently unaware of modular implicits, I have found myself relying a lot on the toplevel via Tuareg. This revealed the following inconvenience: the toplevel definitions accumulate, and very soon you end up with errors such as Error: Ambiguous implicit A: Int/1075 and Int/1023 are both solutions.. Currently, the only solution is to restart the REPL (as far as I know).

One solution would be to remove shadowed modules from the implicit scope. This would prevent errors such as the above from appearing, and provides a way to remove modules from the implicit scope. However, I do not know if this suggestion is innocuous or affects the design of modular implicits.

#46 proposes an explicit keyword to remove a module from the implicit scope, but I presume that this does not allow one to refer to a shadowed module.

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