John Didion

Migrated to `wdl-parsers` repository: https://github.com/openwdl/wdl-parsers/issues/2

Fixed by #522

In the 3/22/23 governance call we decided that WDL v1.2 will include the SHOULD language, with a deprecation warning, and 2.0 will include the MUST language.

@rhpvorderman I like your suggestion of adding a default parameter to `select_first` much better. It avoids adding a new function, and it avoids the ambiguity of my proposed `select_any`. I'll...

@notestaff @aofarrel if you'd still like to see this fixed in earlier versions of WDL (1.0 and earlier) please create a PR adding/updating an ERRATA doc adjacent to those versions...

@mlin Good point. Checksum shouldn't be required. But we can make a suggestion to use checksums or some other means of determining file equality. And to Ruben's point we can...

I agree with @geoffjentry - `Tuple` would be more generally useful than `Pair`. We might want to look at deprecating the later in favor of the former in a future...

If we switch from `Pair` to `Tuple` I'd also get rid of the `left`/`right` naming as well. I'm ambivalent about whether to use array-style indexing vs named elements, e.g., `t.0`...

I think a `find` function would be more generally useful and could be used to determine containment. Since we've already let the regex genie out of the bottle with `sub`,...

Just re-reading this thread and @DavyCats suggestion gave me an idea. AFAIK, this is valid WDL: ```wdl struct MyEnum { String name, String value } workflow test { Object MyEnum...