Fix: Correct GHC optimization flag from -O4 to -O2#96
Merged
Conversation
GHC only recognizes three optimization levels: -O0, -O1, and -O2. The -O4 flag is not valid and is treated as -O2, making it misleading. This change explicitly uses -O2 to enable all recommended optimizations for the executable. Also bump version to 0.9.9.0. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
0e073fd to
ba4bad7
Compare
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR corrects an invalid GHC optimization flag in the executable configuration.
Changes
-O4to-O2in the executable'sghc-optionsRationale
GHC only recognizes three optimization levels:
-O0: No optimization-O1: Moderate optimization-O2: Full optimization (recommended for production)The
-O4flag is not a valid GHC optimization level. While GHC treats it the same as-O2, using-O4is misleading and doesn't follow Haskell best practices. This change explicitly uses-O2to make the optimization level clear and correct.Test Plan
cabal build🤖 Generated with Claude Code