Skip to content

Fix #667 part 2 #668

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

Merged
merged 1 commit into from
May 23, 2025
Merged

Fix #667 part 2 #668

merged 1 commit into from
May 23, 2025

Conversation

phadej
Copy link
Collaborator

@phadej phadej commented May 22, 2025

No description provided.

@phadej phadej force-pushed the issue-667-part-2 branch from 841e2ff to 603c1d7 Compare May 22, 2025 15:32
@dschrempf
Copy link
Collaborator

dschrempf commented May 23, 2025

I know this is a rabbit hole, but I was thinking if removing non-letters could lead to name conflicts. But maybe this is irrelevant in the inlined C code, or should we be concerned with it?

For example, I could think that somebody has a Game.State module, and a GameState data type. (Or is it only the module names that must be unique? Meaning Game/State.hs and GameState.hs would conflict).

Do you think it is better to replace them instead (could also lead to conflicts).

@edsko
Copy link
Collaborator

edsko commented May 23, 2025

I'll merge this as-is for now, as it seems to address the immediate problem at least; if there are still concerns about this, let's open a separate ticket.

@edsko edsko merged commit 6898613 into main May 23, 2025
13 checks passed
@edsko edsko deleted the issue-667-part-2 branch May 23, 2025 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants