Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace input/output set type with tuple type #1207

Closed
pditommaso opened this issue Jun 29, 2019 · 1 comment
Closed

Replace input/output set type with tuple type #1207

pditommaso opened this issue Jun 29, 2019 · 1 comment
Milestone

Comments

@pditommaso
Copy link
Member

The set input/output qualifier allows the definition of tuples of input and outputs. For example:

process foo {
  input:
  set val(x), file(sample) from x
  output:
  set val(x), file('*.bam') into z

  """
  the_command
  """ 
}

The set is misleading because it tends to be read as a verb, while the original intention was to intend it as name i.e. a set of value.

The goal of this issue is to replace it with the tuple keyword which provides a better definition of the associated data structure.

process foo {
  input:
  tuple val(x), file(sample) from x
  output:
  tuple val(x), file('*.bam') into z

  """
  the_command
  """ 
}

The semantic should remain the same as the current set definition.

@pditommaso
Copy link
Member Author

Reminder to myself: add the docs.

pditommaso added a commit that referenced this issue Aug 6, 2019
This commit introduces a new input/output qualifier
named `tuple` which replaces the `set` qualifier.

The semantic remains unchnaged. The rational of this change
is purely from a syntactic/expressiveness point of view.
@pditommaso pditommaso added this to the v19.10.0 milestone Jan 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant