-
Notifications
You must be signed in to change notification settings - Fork 0
Avoid sets of simples #386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Could we enhance this to actually remove |
feb94a6
to
d832a12
Compare
bd4dad1
to
27cce55
Compare
Anyone know why the tests aren't running for this? @mshinwell? Should be ready for final review and merge otherwise |
@lukemaurer I think it's because you need to rebase, there is a conflict |
A `Name.Set.t` or `'a Name.Map.t` is a fine thing, but a `Simple.Set.t` or `'a Simple.Map.t` is much sketchier, since whether we want to treat two simples that differ only in `Rec_info.t` as equivalent depends on context. Fortunately, we usually just need a set or map of names. The one place where this gets tricky is in the uses of `Aliases.get_alias`, so there's now `Aliases.Alias_set.t` to encapsulate the needed operations.
Everything is now gone except for a few stragglers in `cmx/` and `naming/`; these will be more easily dealt with after some changes to `Simple.t`.
27cce55
to
7f1dec6
Compare
Rebased (freaking |
request-checks: true
Actually making the change (which would require significantly refactoring `Typing_env.add_equation`) is outside the scope of this PR.
I agree to merge if the |
A
Name.Set.t
or'a Name.Map.t
is a fine thing, but aSimple.Set.t
or
'a Simple.Map.t
is much sketchier, since whether we want to treattwo simples that differ only in
Rec_info.t
as equivalent depends oncontext. Fortunately, we usually just need a set or map of names. The
one place where this gets tricky is in the uses of
Aliases.get_alias
,so there's now
Aliases.Alias_set.t
to encapsulate the neededoperations.