Skip to content

Tweak documentation (mostly for dependentTestGroup)#467

Merged
Bodigrim merged 1 commit intomasterfrom
documentation
Mar 5, 2026
Merged

Tweak documentation (mostly for dependentTestGroup)#467
Bodigrim merged 1 commit intomasterfrom
documentation

Conversation

@Bodigrim
Copy link
Collaborator

Closes #443 and also fixes a bunch of Haddock warnings.

@martijnbastiaan @Raveline could you please review?

@Bodigrim
Copy link
Collaborator Author

@martijnbastiaan @Raveline just a gentle reminder; I think you are the best positioned to review this documentation.

Copy link
Contributor

@martijnbastiaan martijnbastiaan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good! Thanks for the effort.

#endif

-- | @computeStatistics@ computes a summary 'Statistics' for
-- | @computeStatistics@ computes a summary t'Statistics' for
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, learned myself something new.
Yet the t qualifier is default, so not really needed here:
From: https://haskell-haddock.readthedocs.io/latest/markup.html#hyperlinking-and-re-exported-entities

Since values and types live in different namespaces in Haskell, it is possible for a reference such as 'X' to be ambiguous. In such a case, Haddock defaults to pointing to the type. The ambiguity can be overcome by explicitly specifying a namespace, by way of a v (for value) or t (for type) immediately before the link

But of course, does not hurt.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really know why but without t'...' cabal haddock keeps spamming warnings about "ambiguity", very annoyingly.

@Bodigrim Bodigrim merged commit 3699165 into master Mar 5, 2026
16 checks passed
@Bodigrim Bodigrim deleted the documentation branch March 5, 2026 23:04
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.

Improve documentation for sequentialTestGroup

3 participants