← Back to index | Original Bugzilla link

Bug 15767 – Why isn't there a deprecation plan for TypeTuple?

Status
RESOLVED
Resolution
WONTFIX
Severity
enhancement
Priority
P1
Component
phobos
Product
D
Version
D2
Platform
x86_64
OS
Linux
Creation time
2016-03-06T01:14:00Z
Last change time
2016-03-07T16:10:55Z
Assigned to
nobody
Creator
greeenify

Comments

Comment #0 by greeenify — 2016-03-06T01:14:01Z
I read that TypeTuple is an alternate name for AliasSeq for legacy compatibility. https://github.com/D-Programming-Language/phobos/blob/master/std/typetuple.d If it's legacy, why is there no @deprecated and no deprecation plan for std.typetuple?
Comment #1 by issues.dlang — 2016-03-07T02:22:48Z
Please don't create bug reports that are questions. If you want to ask a question, then ask in the newsgroup. I believe that the primary reason that TypeTuple isn't deprecated is that it's used a _ton_, and deprecating it would result in a flood of deprecation messages in many projects. And while personally, I really don't like leaving aliases like this around, I don't think that either Walter or Andrei think that it's all that big a deal. So, while we may yet deprecate TypeTuple and move towards getting rid of it, there isn't much of a hurry to do so.