Rejecting "any" as bounded type name?

Paul Benedict pbenedict at
Thu Jul 9 16:13:45 UTC 2015

I know "any" is going to be a context-sensitive keyword, but I wonder if
there is merit in restricting "any" as a name of a bounded type name?

I don't see much comprehension value in seeing (1) List<any any> or (2)
List<any> without specialization. I truly dislike syntax puzzlers, and I
think my idea would help readability and eliminate gotchas. Thoughts?


More information about the valhalla-dev mailing list