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
Credit to @adthrasher for the idea proposed in a comment on #133
We have DisallowedInputName and DisallowedOutputName. Those should remain unchanged, but there should be a new rule that checks all Decls (IO and private) for "type prefixes/suffixes". e.g. File gtfffile would be bad and so would Int my_int
The text was updated successfully, but these errors were encountered:
One consideration (via Mike Rusch), what about something like bcftools annotate (https://samtools.github.io/bcftools/bcftools.html#annotate). It has parameters that can be specified as a string or as a file. So the file suffix might make sense in that case to distinguish.
-r, --regions chr|chr:pos|chr:from-to|chr:from-[,…]
see [Common Options](https://samtools.github.io/bcftools/bcftools.html#common_options)
-R, --regions-file file
see [Common Options](https://samtools.github.io/bcftools/bcftools.html#common_options)
Credit to @adthrasher for the idea proposed in a comment on #133
We have
DisallowedInputName
andDisallowedOutputName
. Those should remain unchanged, but there should be a new rule that checks all Decls (IO and private) for "type prefixes/suffixes". e.g.File gtfffile
would be bad and so wouldInt my_int
The text was updated successfully, but these errors were encountered: