dedent VS proposal-private-fields

and so `dedent` would not strip any indentation. That is, `dedent` is meant to identify the maximal common leading indentation in the template as written by the developer, which should not depend on the values of the interpolands.

A stale GitHub issue on the dmnd/dedent repo has a real-world example where this matters and led to a subtle bug: https://github.com/dmnd/dedent/issues/22

There is also some other interesting use cases.

> - # private... not sure why they didn't just use the "private" keyword, but I don't care. I almost always use TypeScript anyways

One of the reasons was to allow private and public fields of the same name, so that subclasses are free to add own public fields without accidentally discovering private fields. There were many more considerations that went into the design: https://github.com/tc39/proposal-class-fields/blob/main/PRIV....

There was a heated debate about this and the choice of the # sigil back in 2015 at the time private fields were being designed: https://github.com/tc39/proposal-private-fields/issues/14.

The inability to correctly polyfill this, which still keeping the variables private, was a subject of debate in TC39. One of the explicit advantages of moving to a "soft private" model (as discussed here: https://github.com/tc39/proposal-private-fields/issues/33) was that it could be polyfilled correctly.

There was a long and thoughtful article explaining why the private keyword was not enough; but now I can't find it :-( Here's the best replacement I could find: https://github.com/tc39/proposal-private-fields/issues/14 Effectively, what they are saying, is that you need to be able, within a class method, to disambiguate whether you are dealing with a private field of an identically named public field, and the keyword doesn't help with this.

This is all covered here:

https://github.com/tc39/proposal-private-fields/blob/master/...

As well, the Issues section of that proposal repo, as well as the Issues section of the original Private Fields repo (before it was merged with the Class Fields proposal) contain lots of discussion about this topic.