Skip to content
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

Consider supporting fixity namespacing #1113

Open
amesgen opened this issue May 21, 2024 · 1 comment
Open

Consider supporting fixity namespacing #1113

amesgen opened this issue May 21, 2024 · 1 comment

Comments

@amesgen
Copy link
Member

amesgen commented May 21, 2024

-- TODO Support fixity namespacing?
-- https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0065-type-infix.rst
--
-- Note that currently, our fixity machinery does *not* do any namespacing:
--
-- - https://github.com/tweag/ormolu/pull/994#pullrequestreview-1396958951
-- brought this up in the past
--
-- - https://github.com/tweag/ormolu/pull/1029#issue-1718217029
-- has a concrete example (morley-prelude) where namespacing would matter

#1103 (comment)

@mrkkrp
Copy link
Member

mrkkrp commented Jun 13, 2024

It looks like we should wait till fixity declarations without type or data keywords start to pertain exclusively to values. If my understanding is correct, then right now fixity declarations without type or data keyword still pertain to both values and types, so we would have to fallback to the current "common namespace" treatment even if we introduce the distinction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants