You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Env.get reports an error inside stdlib env.kex instead of the call site #562
Writing Env.get (instead of the env capability, or ENV) blames the stdlib, not the user's code:
main do
IO.printLine(Env.get("HOME").or("?"))
end
../../src/stdlib/env.kex:25:1: error: this file is `Env` by its path, but declares `ENV`; name it `module Env`
The error points at src/stdlib/env.kex and tells the user to rename a stdlib module. It should say that Env is not a module, and suggest main(args, env) → env.get(...) (or ENV). It looks like Env. triggers a path-based module lookup that finds env.kex and then fails the file-name/module-name consistency check on it.
Confirmed on main (fc2586f), both backends: IO.printLine(Env.get("HOME").or("?")) in main reports src/stdlib/env.kex:25:1: error: this file is Envby its path, but declaresENV; name it module Env`` instead of an error at the call site.
Activity
akoskovacs commentedon Oct 24, 2026
Confirmed on
main(fc2586f), both backends:IO.printLine(Env.get("HOME").or("?"))inmainreportssrc/stdlib/env.kex:25:1: error: this file isEnvby its path, but declaresENV; name itmodule Env`` instead of an error at the call site.