1lab/mikan
13
52
Fork
You've already forked mikan
9

WIP: feat: redo makefile #49

Closed
pounce wants to merge 1 commit from pounce/mikan:magical-mikan-makefile into main
pull from: pounce/mikan:magical-mikan-makefile
merge into: 1lab:main
1lab:main
1lab:aliao/occurs-opt
1lab:aliao/rec-con
1lab:fix-license
1lab:aliao/oopsie
1lab:aliao/strengthen-iapply
Contributor
Copy link

This commit adds a tiny makefile that exists entirely to run cabal. It
should make it easier for people to figure out how to run tests and
select certain test suites for the first time.

This commit adds a tiny makefile that exists entirely to run cabal. It should make it easier for people to figure out how to run tests and select certain test suites for the first time.
feat: redo makefile
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
cb28256646 
This commit adds a tiny makefile that exists entirely to run cabal. It
should make it easier for people to figure out how to run tests and
select certain test suites for the first time.
pounce changed title from (削除) feat: redo makefile (削除ここまで) to WIP: feat: redo makefile 2026年04月27日 14:24:53 +02:00
@ -8,2 +7,3 @@
GFLAGS ?= +RTS -A128M $(GHC_RTS_OPTS) -RTS
TOP=.
CBFLAGS ?= --semaphore -O1 --ghc-options="$(GFLAGS)" -foptimise-heavily
Contributor
Copy link

Wouldn't it make more sense to move at least the -foptimise-heavily to the cabal.project? It feels weird to have three places which specify defaults for flags (Mikan.cabal sets original defaults, cabal.project sets -fdebug, and the Makefile sets -foptimise-heavily)

Wouldn't it make more sense to move at least the `-foptimise-heavily` to the `cabal.project`? It feels weird to have three places which specify defaults for flags (Mikan.cabal sets original defaults, cabal.project sets `-fdebug`, and the Makefile sets `-foptimise-heavily`)
Author
Contributor
Copy link

closing in favor of #136

closing in favor of #136
pounce closed this pull request 2026年06月26日 15:30:36 +02:00
All checks were successful
ci/woodpecker/pr/test Pipeline was successful

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
1 - scope
language
 Backwards-compatible changes to the surface language, such as adding new features.
1 - scope
language change
 Breaking changes to a documented part of the surface language. These should be documented and specifically called out in the changelog.
1 - scope
performance
 Semantics-preserving performance work.
1 - scope
task
 Changes that are not apparent to the user, e.g. developer documentation and refactors, which do not need to be documented.
A: dead-code
Dead code elimination and --save-metas.
A: errors
Reporting of error and warning messages.
A: highlighting
Highlighting during interaction & literate compilation
A: imports
Handling of imports and interface file de/serialization.
A: infra
Iinfrastructure (e.g. CI, developer documentation, the build system, or the repository itself)
A: instance
Instance declarations, arguments, and resolution
A: lhs
LHS checking, coverage checking, and clause compilation
A: modules
Declaration and instantiation of parametrised modules.
A: parallel
Parallel typechecking.
A: positivity
Positivity checking
A: printing
Pretty-printing, display forms, and the wording of diagnostic messages
A: records
Record declarations, record expressions and copattern matching
A: scoping
Scope checking (ConcreteToAbstract)
A: termination
Termination checking
0 - type
bug
 Issues describing an incorrect behaviour in the project, typos in the documentation, etc.
0 - type
discussion
 An issue raised to gather opinions on a proposed change, or a suggested language change.
0 - type
question
 An issue raised to ask a question.
9 - status
duplicate
 This issue or pull request already exists.
9 - status
info needed
 More information is needed from the submitter to decide how to proceed with the issue report.
9 - status
invalid
 The issue report or pull request does not describe an actual bug, or does otherwise does not meet the contributing guidelines.
good first issue
Interested in contributing? Get started here.
upstream
Related to an upstream repository, already reported there
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
1lab/mikan!49
Reference in a new issue
1lab/mikan
No description provided.
Delete branch "pounce/mikan:magical-mikan-makefile"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?