Are these types open to manipulation like normal "fiat" JS types? For example, what would happen if I instantiated an object, and then some unscrupulous third party "manipulated" its .prototype field to point to a different class' prototype? Would I still be able to brag to my friends about my special NFT type and post selfies on social media, or would I simply be holding what amounts to be a very fancy pointer?

There might be an uncountable number of types, but we can only define a countable quantity of them. They are still a lot, but this is a big step towards scarcity.

I would like to buy symbol. Do you accept payment in pennies?

Are these types open to manipulation like normal "fiat" JS types? For example, what would happen if I instantiated an object, and then some unscrupulous third party "manipulated" its .prototype field to point to a different class' prototype? Would I still be able to brag to my friends about my special NFT type and post selfies on social media, or would I simply be holding what amounts to be a very fancy pointer?

I'm not sure, I hadn't put a lot of thought into what @craftytrickster‍s like you might do with these.

What if a right-clicker just copies and pastes my types? 😕

To make things more economically viable, owners of type A should get a comission when someone mints a type that is assignable toA. With that said I would like to claim interface { toString(): string }.

Can we start calling type artists "tartists"? Who wouldn't want to be a tartist? 😉

Has the environmental impact of this proposal been considered? I've heard "proof of steak" is better for that, should we leave steaks on TS team members' desks with a note of which type we wish to claim?

It should be noted that in order for types to be truly non-fungible, we first need to switch to nominal typing. Otherwise class A {} and class B {} are fungible!

should we leave steaks on TS team members' desks

There's prior art here courtesy of @JoshuaKGoldberg: #29374 (comment)

Essentially, leave cakes not steaks. 🎂

I've been waiting for this announcement:

export type OptionalCat = { cat?: string, name: string };
export type DefiniteCat = { cat: string, name: string };
export type OptionalDog = { dog?: string, name: string };
export type DefiniteDog = { dog: string, name: string };

Up until now I was only able to assume nobody else had ever stolen these types.

Similar concept being considered over at csharplang: dotnet/csharplang#5976

I like this idea but how will this be enforced? I think if we use a trust model then the right clickers will just use our types without permission. Would it be feasible to connect TypeScript to the blockchain to verify that you can actually use the types you're attempting to? I think this would go a long way to protect the copyright of all tartists.

A lot of you have raised the risk of right-clickers copying precious types.

I will reach out to partners on our editor teams to see if we can fix this. I think if Visual Studio and Visual Studio Code lead the pack, we may be able to disable right-clicking in TypeScript files in all editors!

Admittedly, I'm not that well-connected. To start small, does anyone have the phone number for the CEO of the nano editor corporation?

Admittedly, I'm not that well-connected. To start small, does anyone have the phone number for the CEO of the nano editor corporation?

You might have luck with 248-434-5508.

does anyone have the phone number for the CEO of the nano editor corporation?

Try 0118 999 881 999 119 7253.

@MartinJohns I think now that you mention it, I've seen this number for their hotline. It's a long one, but luckily they have a catchy jingle!

I have a concern about typeconomics.

Wouldn’t it help the adoption to pay tartists per error than per use? (based on error length ofc)
I’m a huge fan of this endeavor, and I’d like to ensure we are truly going to the moon 🚀🌙

On another note, when is the Non-Fungible-Type Marketplace plugin coming to TS Playground?

And to think, up until now I've just been busking UnionToIntersection definitions in subways and public parks for spare change!

What if a right-clicker just copies and pastes my types? confused

Let's doubleclick it.

I'd like to make a bid for Window and Document - I have a feeling these are going to see some use in the future.

To ensure artificial scarcity to keep the Non Fungible Types values high, we could introduce a form of proof of work - I would propose that the typescript compiler will support mining types, for registering a type TSC will first try to find a 32 bit nonce that would satisfy sha256(sha256(source of the type without spaces + nonce)). Integrating WebGPU in TypeScript could be helpful to do it in a reasonable amount of time and seems fair that a developer has to have a powerful GPU to compile typescript code. A new command line argument "tsc --nft file.ts" would be handy to have an interactive NFT registration experience.

interface Monke {
    get ugliness(): number;
    eat(what: Banana): void;
    beHappy(): never;
}

original type do not steal

I'm starting to suspect this was an April Fools' joke and not the future of TypeScript. Perhaps you meant to add the tag Community Fooling instead of Community Tooling?

@fatcerberus I made my own Monke type, too!

interface Monke {
    get ugliness(): number;
    eat(banana: Banana): void;
    beHappy(): never;
}

plz no steel

Thanks for the feedback everyone! I see a bright future for the --noImplicitFunging flag.

We are looking into revoking Daniel's issue-filing permissions.

Someone else can use symbol. It's whatever.

I am gladly donating never and unknown to @ahejlsberg so that I never have to explain them again.

🤣