Another patch for Nominal Type

In [this article](https://spin.atomicobject.com/2018/01/15/typescript-flexible-nominal-typing/), as a introduction to another thing, the author shows another kind of patch to use nominal types:

```ts
interface PersonIdBrand { _type: "Person"; }
type PersonId = PersonIdBrand & number;

interface BlogPostIdBrand { _type: "BlogPost"; }
type BlogPostId = number & BlogPostIdBrand;
```

It worked better for me with type inference than [your approach with enums](https://basarat.gitbook.io/typescript/main-1/nominaltyping#using-enums).

Do you think that is a good idea to add this alternative? or is there a well known issue with this approach?

Compare the alternative nominal-typing pattern in the linked Atomic Object article with the existing enum approach in the book's nominal typing section. Check its type-inference behavior and any documented limitations before deciding whether it belongs. Done means reaching a clear inclusion decision and defining the explanation and examples needed if it is added.

Written by the indexing model from the issue text.