-
Notifications
You must be signed in to change notification settings - Fork 8
Add the cabal guide to application profiling #9
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
|
An additional call to action to help with documentation at the the end would be nice, with a reference to https://blog.haskell.org/documentation-best-practices-in-2024/ |
|
@malteneuss Thanks! I wrote something at the end. Is it good enough? |
| tags = ["Performance", "Profiling"] | ||
| +++ | ||
|
|
||
| The [Cabal Manual][Cabal Manual] now has a guide on how to analyse the performance of Haskell applications. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still disagree with "analyze the performance of Haskell applications". My version:
| The [Cabal Manual][Cabal Manual] now has a guide on how to analyse the performance of Haskell applications. | |
| The [Cabal Manual][Cabal Manual] now has a guide on how to enable profiling in Haskell projects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's have this conversation in haskell/cabal#10606 first.
086404f to
82f7fb1
Compare
Looks good, thanks. |
82f7fb1 to
e08df3e
Compare
e08df3e to
50afb36
Compare

cc @malteneuss @jasagredo @ulysses4ever please review