Opaque type field sharing a name with a function can cause indeterministic compiler errors

[sbergen]

Given a main package source file of

import foo
import gleam/io

pub fn main() {
  let foo = foo.make_wibble()
  foo.wobble()
  io.println("edit this line to change state")
}

and a module foo (this has to match name used in the let binding!) with

import gleam/io

pub opaque type Wibble {
  Wibble(wobble: Int)
}

pub fn wobble() {
  io.debug("edit this line to change state")
}

pub fn make_wibble() -> Wibble {
  Wibble(1)
}

Depending on which file has been edited last, the program will either run fine, or report

error: Type mismatch
  ┌─ /home/sbergen/source/repro/src/repro.gleam:6:6
  │
6 │   foo.wobble()
  │      ^^^^^^^

This value is being called as a function but its type is:

    Int

Gleam version: 1.6.3

[GearsDatapacks]

This is probably due to a caching issue. Changing based on last edited file is something I've noticed before with issues related to the module cache

[lpil]

Does this happen with the nightly version also?

[sbergen]

Does this happen with the nightly version also?

Reproduces in gleam 1.6.2-nightly-20241219 also.