Hello, any feedback about this PR ? 😃

Yeah, I include this in my global .d.ts file for every project. Would be nice to have it in the main lib 👍

Yes, I'd much prefer for Omit<T, K> to be part of TypeScript itself rather than having to self-define.

@DanielRosenwasser @RyanCavanaugh Hi ! What is the futur of this PR ?

• We didn't want to conflict with other Omits that had different behavior - and it would conflict with a global.
• You're going to run into global scope problems anyway.
• But you might not, so why are you intentionally breaking people?
  All Omit I saw actually are doing the same. And if it's not the case :

• Others will rename their Omit type.
• You can call it WhatEverYouWant

This argument doesn't prevented you to create other generic type.
But it will just help 95% of people.

• But there are at least 2 different versions of Omit that are duplicated over DefinitelyTyped

All I see are 50 duplicate of the same type Omit, or previous declaration without Exclude, but doing the same thing. And you say it, it's duplicated ; let's stop this.

• Also, this uses Exclude on a generic, so maybe you want to wait for negated types?

What is this ?

It looks like you've sent a pull request to update our 'lib' files. These files aren't meant to be edited by hand, as they consist of last-known good states of the compiler and are generated from 'src'. Unless this is necessary, consider closing the pull request and sending a separate PR to update 'src'.

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.