Brett Zamir

Related to this, when using a rest element within a destructured array: ```js /** * @param {GenericArray} cfg * @param {number} cfg.0 * @param {...string} cfg.1 * @returns {void} */...

@theabhinavdas : JSDoc blocks typically go above the *definitions* (or declaration)--not where a function is used. And even when one does document the return value of a function, it typically...

+1 for `typeof`. In my case, I'm also interested in a future/Typescript-compatible way for pointing to an argument supporting a `@callback` signature or a specific method of an `@interface` (and...

Imho, JSDoc just isn't moving quickly enough to update its type parser to work with TypeScript's flavor of JSDoc. At the most basic level, the community needs something like TypeScript's...

Only steps 1 and 2 should be necessary, and step 2 only if you wish other projects to use your code, noting that for step 1, TypeScript-style documentation syntax *is*...

Step 2 is optional. You need a declaration file if you want third parties to use your code in a type-aware manner (unless [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) has already made type files on...

It is true that those types are not accepted by JSDoc's type parser, but the fact is that the development pace of TypeScript to accommodate all kinds of important needs...

+1 for TypeScript

@BlackWild : I am not a regular user of it, but I believe you may find tools that work against TypeScript, since it is [generally](https://stackoverflow.com/questions/29918324/is-typescript-really-a-superset-of-javascript) a strict superset of JavaScript....

This is pretty significant as it is completely the opposite. As with #24 , I think this could merit a whole new category since "Unlicensed" is not really "uncategorized" (though...