chapel-lang/chapel — pull request #1026 by bradcray (2014-12-17 23:14:16+00:00)
Title: Adding one typeselect future and one test showing its pointless

twoTypeSelects.chpl shows that the current implementation of
type select does not support multiple type selects in a single
Chapel program. D'oh! It's probably a five-minute fix to get
this working if one cared to. By the time I'd written up the
description in the .future, it seemed like I also had the
solution. But...

deprecateTypeSlect.chpl shows the syntax I'd prefer to use for
"type select" statements and was intended as a feature request
future; but it turns out to work. So it raises the question
"Do we even need a type select anymore?" Until someone argues
convincingly otherwise, my answer is "no, it seems like we
don't."