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
As mentioned in the comments GH-949, there is currently no proper documentation for clash and clashi specific flags. These should be included somewhere which is easy to find, and clearly explains what the purpose and default values of different flags are.
On a related note, running clash --show-options currently does not show any clash specific options (e.g. anything starting with -fclash-OPT currently isn't printed. This also makes it more difficult for users to know what clash-specific flags are available.
The text was updated successfully, but these errors were encountered:
Update: With regards to clash --show-options not showing all options, it appears that the list of flags to print in the GHC specific modules do not include the common flags from Clash.GHC.ClashFlags.
When calling clash with the --show-options flag, it now prints
all options, including common clash options which were previously
not being shown. It remains to be seen how to document all the flags
which are added by clash (instead of GHC).
When calling clash with the --show-options flag, it now prints
all options, including common clash options which were previously
not being shown. It remains to be seen how to document all the flags
which are added by clash (instead of GHC).
As mentioned in the comments GH-949, there is currently no proper documentation for
clash
andclashi
specific flags. These should be included somewhere which is easy to find, and clearly explains what the purpose and default values of different flags are.On a related note, running
clash --show-options
currently does not show any clash specific options (e.g. anything starting with-fclash-OPT
currently isn't printed. This also makes it more difficult for users to know what clash-specific flags are available.The text was updated successfully, but these errors were encountered: