Conversation
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
|
I'm not sure about introducing such slight variation in the lang, this let to sub-dialect with minor, annoying incompatibilities across java, groovy and different nextflow versions |
|
In the specific case likely a better solution would be a type linter or checker to avoid a number is assigned to time/duration field |
|
Type checking won't really help here because a duration field can be initialized from a number, string, or duration literal. As for syntax changes, I agree in general about not changing things that don't need to be changed. That's why I left the numeric syntax unchanged. But if some syntax is never used in Nextflow and creates foot-guns, I think it's fair to remove. Especially right now when we are refining the Nextflow language spec. |
|
The |
Remove literal suffixes like
7d,7f,7L, since they are not needed in Nextflow and can lead to syntax ambiguities (e.g.7dversus7.d)