René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Suggestion: typedefs","articleBody":"**Suggestion: Allow typedefs for aliasing types, class names and interface names**\n\nUse case:\n\n``` javascript\n// 1. Use case overlaps with interface functions types and is even uglier\ntypedef (number) =\u003e number MyCallback;\n\n// 2. With generics\ntypedef Vector\u003cSomeDataType\u003e MyVector;\n\n// 3. With primitive data types\ntypedef string MyData;\n\n// 4. Aliasing classes and interfaces\ntypedef ReallyLongClassName ShortName;\ntypedef otherModule.subModule.subModule.Runnable Runnable;\n```\n\n**Question: Do we need them?**\n1. Assigning a name to function types is already possible using [interface function types](http://www.typescriptlang.org/Handbook#interfaces-function-types). In my opinion, their syntax is nicer and we should not introduce another syntax for the same feature.\n2. This can help minimzing the amount of typing.\n3. According to the last comment of the [original CodePlex issue](http://typescript.codeplex.com/workitem/119), this can help commenting the code. It does however introduce another layer of name aliasing for names which are already short (`number, string, boolean`).\n4. This can also help minimzing the amount of typing, especially for accessing external classes and interfaces inside deeply nested modules. Aliasing modules themselves would also be imaginable.\n\n---\n\nThe original CodePlex issue: http://typescript.codeplex.com/workitem/119\nNote that many of the given code examples are already covered by #14 (union types).\n","author":{"url":"https://github.com/ComFreek","@type":"Person","name":"ComFreek"},"datePublished":"2014-07-30T10:56:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/308/TypeScript/issues/308"}