You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The old DebugLevel style debug options are replaced with a more
granular style, where different options can be set independently.
This allows things not previously possible, such as counting
transformations without having to print any normalized core.
The old -fclash-debug flag still works for backwards compatibility.
Additional command line flags are now available to directly set
options from the new type:
-fclash-debug-invariants checks for invariants and displays
warnings / errors. Setting this alone is equivalent to DebugSilent.
-fclash-debug-info sets the amount of information to display
when applying transformations. This overlaps a lot with the old
DebugLevel type, but is named more consistently.
-fclash-debug-count-transformations counts the number of
transformations applied (without showing any normalized core
like DebugCount did)
CHANGED: Clash now supports more expressive debug options at the command line [#1800](https://github.com/clash-lang/clash-compiler/issues/1800).
2
+
3
+
With the old `DebugLevel` type for setting debug options, it was not possible to set certain debug options without implying others, i.e. counting transformations was not possible without also printing at least the final normalized core for a term. It is now possible to set options individually with new flags:
4
+
5
+
* -fclash-debug-invariants to check invariants and print warnings / errors
6
+
* -fclash-debug-info to choose how much information to show about individual transformations
7
+
* -fclash-debug-count-transformations to print a tally of each transformation applied
8
+
9
+
The old -fclash-debug flag is still available for backwards compatibility, and each `DebugLevel` is now a synonym for setting these options together.
0 commit comments