Skip to content

Conversation

@Kleidukos
Copy link
Member

@malteneuss
Copy link

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/

@Kleidukos
Copy link
Member Author

Kleidukos commented Nov 28, 2024

@malteneuss Thanks! I wrote something at the end. Is it good enough?
image

tags = ["Performance", "Profiling"]
+++

The [Cabal Manual][Cabal Manual] now has a guide on how to analyse the performance of Haskell applications.

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:

Suggested change
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.

Copy link
Member Author

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.

@Kleidukos Kleidukos force-pushed the cabal-performance-analysis-guide branch from 086404f to 82f7fb1 Compare November 28, 2024 20:04
@malteneuss
Copy link

@malteneuss Thanks! I wrote something at the end. Is it good enough?

Looks good, thanks.

@Kleidukos Kleidukos force-pushed the cabal-performance-analysis-guide branch from e08df3e to 50afb36 Compare December 23, 2024 09:59
@Kleidukos Kleidukos merged commit 2e105e2 into main Dec 23, 2024
2 checks passed
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.

5 participants