Skip to content

Compiler loses track of existing modules #5983

@fabientownsend

Description

@fabientownsend

Environment

Erlang/OTP 19 [erts-8.3] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Elixir 1.4.2

  • Operating system: OS X El Capitan

Current behavior

  1. Duplicate a module
  2. Remove the methods from the duplication but keep the module name
  3. Run mix test, it will find the duplication without the method and complain that the methods don't exist
  4. Delete the duplication of the module
  5. Run mix test, it doesn’t find original module anymore and still complaining that it can't find the method

I assume there are some leftover .beam files floating about… and it doesn't pick up that there is another original module to compile now

To solve this problem I had to:

  1. rename the original module
  2. save
  3. rename it to its original name
  4. save

after that the compilation work

Expected behavior

To not loose track of the existing module if they still exist?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions