query: "for all ... do in parallel" without "end for"
positive_passages.docid: 27110
positive_passages.text: algpseudocode without end block text
negative_passages.docid: 59095
negative_passages.text: What is the opposite of "parallel" in architecture?
negative_passages.docid: 130414
negative_passages.text: options for [for /f "usebackq" %%f in (`find "" path`) do] sentence in batch
negative_passages.docid: 131035
negative_passages.text: "every" vs "each"?
negative_passages.docid: 107960
negative_passages.text: Code block passed to each works with brackets but not with 'do'-'end' (ruby)
negative_passages.docid: 123511
negative_passages.text: Writing a recursive block 'while'
negative_passages.docid: 84834
negative_passages.text: Does *first of all* always go with *second of all*?
negative_passages.docid: 85198
negative_passages.text: What do we mean when we say "for all n where n is an element of..."
negative_passages.docid: 101892
negative_passages.text: Alternatives to "and/or"?
negative_passages.docid: 71134
negative_passages.text: Parallel iterator in Scala
negative_passages.docid: 102758
negative_passages.text: "Not only ... but also" —parallelism in a particular case
negative_passages.docid: 127600
negative_passages.text: When can I "do, do" something?
negative_passages.docid: 28671
negative_passages.text: Is it correct to use two present participles sequentially?
negative_passages.docid: 64832
negative_passages.text: "do ... while" loop equivalent in Mathematica
negative_passages.docid: 53155
negative_passages.text: Using bare infinitive after 'does'
negative_passages.docid: 132176
negative_passages.text: Precedence of && over ||
negative_passages.docid: 78
negative_passages.text: Why is using "for...in" for array iteration a bad idea?