Shagen Ogandzhanian
Shagen Ogandzhanian
Well, `@nativeInvoke` is the only way to translate this correctly in my understanding so I'd rather investigate how to supress this warning for this particular declarations.
Thank you for this report. I'll take a look!
Here are some real-life examples: ```typescript // very obvious type TransformFunction = (this: TransformContext, value: S) => void; type FlushFunction = (this: TransformContext) => void; declare function onHeaders(res: ServerResponse, listener:...
What makes things worse - we can not have function type with receiver in external declarations
Related issue in Kotlin - https://youtrack.jetbrains.com/issue/KT-15140
Can you please provide some code you are trying to convert.
A-ha! Now it's clearer, thank you! If it's a syntactically valid construction (which it seem to be) we still need to support it. It's very strange to me that it's...
Here's relevant quote [from documentation](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-6.html#get-and-set-accessors-are-allowed-in-ambient-contexts) that explains the rationale behind translating getters and setters: ### `get` and `set` Accessors Are Allowed in Ambient Contexts In previous versions of TypeScript, the...
Can you please provide a snippet of code what you'd rather expect to have as a result?
@ScottPierce just have a clearer picture - why exactly you are trying to compile all of them rather than just index.d.ts? Of course, my question does not imply, however, that...