@Ikuyadeu, thanks for your PR! By analyzing the history of the files in this pull request, we identified @egamma, @jrieken and @Tyriar to be potential reviewers.

We cannot merge that yet

• we use typedoc to generate the extension API page and that isn't fit for TypeScript 2.0 yet
• it's unsure how readonly-ness should be expressed for objects we have created vs objects consumer create, e.g TextEditorOptions cannot be modified by setting a value ala options.lineNumbers = value but when creating a new objects they can

Thank you.
So, I should close this PR once, or wait until typedoc to version up?
Can I be of any help for it?

We are ready for this and want it for Jan

@Ikuyadeu Can you also add readonly here (basically I have searched for @readonly)

• https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L1599
• all in env (https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3379)
• https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3863
• https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3914

Can the @readonly comment annotations be removed now?

@jrieken Ok,

• https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L1599
  added redonly.But,

• all in env (https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3379)

• https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3863

• https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3914
  are yet. because they're using export and namespace.

re #13863 (comment) I wanna first check how the doc generation tool handles the native readonly flag.

re #13863 (comment) Thanks. Didn't know that

@jrieken Sorry, I missed

Reopened PR in #18251