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
Commit 886d5dc
Browse filesBrowse the repository at this point in the historyBrowse files
Follow a functor's aliases to its file for the members it creates
Review fix: a functor from another file applied through a local alias,
such as `module Make = AppliedFunctor.MakeSet` then `Make(IntOrd)`, kept
the alias as the members' source, so Go to Definition and type-definition
links pointed into the caller at the functor's line numbers, and uses
didn't reach the functor's references and renames. The source is now the
path the compiler resolved the alias chain to, through modules too.
Analysis modified (go to definition of an applied member):
Example:
module Make = AppliedFunctor.MakeSet
module Aliased = Make(AppliedFunctor.IntOrd)
let a = Aliased.add([], 1)
Before (text): definition of `add`
file:///AppliedFunctorUse.res 7:6-7:9
After (text): definition of `add`
file:///AppliedFunctor.res 7:6-7:9
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Kr4cjoUi2f5VpMvE6wT9bo
Signed-off-by: Christoph Knittel <ck@cca.io>
0 commit comments