John Didion

The spec now explicitly states that a coercion from `read_json` return value to a specific type is requires. In WDL 1.2 we will add the optional second parameter to `read_tsv`...

@giangndm sure that would be great. I can add you as a collaborator on my fork. I'd you have a good plan for finishing the implementation go for it.

That would be great, thanks! I'll add you as a contributor.

@ozgunozerk the big outstanding issue is implementing `next_ver::Updater::get_diff` for a git-only package. I'm thinking we need some higher level interface which can abstract whether the package information is coming from...

@MarcoIeni @ozgunozerk I introduced the `BasePackage` enum and did a bit of refactoring. Now I think the only thing left is to implement the `Repository` case for the three functions...

The parameter and return types of the standard library functions are given as explicitly as possible. Some functions are generic and thus the return type depends on the input type(s)....

This seems to be a common issue people encounter with installing python packages using conda, for example see https://www.biostars.org/p/9522705/#9522724. I believe it is due to a conflict between your python...

Agree with Patrick - this is true at least for the ANTLR parser. But I support adding clarification to the spec.

You're right...we should genericize length.

The PR never got moved, but I don't see any reason to keep it open. Would be nice if @luyang93 or someone else could move it so the changes don't...