We’re joined this week by Max Heiber who is part of a team at Bloomberg implementing #private fields in TypeScript, Daniel Rosenwasser who is the program manager for the TypeScript team at Microsoft, and Ryan Cavanaugh who is a developer on the TypeScript team at Microsoft. Naturally, we’ll be talking about the ECMAScript #private field proposal and how its implementation affects TypeScript—which already has a type of private field that uses the private keyword.
As you might expect, there’s a lot to cover from how we even talk about the two different approaches, the functional differences between the two approaches, whether anyone should transition from the private keyword to #privates, to the challenges of implementation. Our discussion takes a few tangents related to private fields including the upcoming public field initializers, whether to expect anything like the private/#private divergence in the future, and type annotations in comments.
Nick Nisi on Twitter
Neil Roberts on Twitter
Max Heiber on Twitter
Daniel Rosenwasser on Twitter
Ryan Cavanaugh on Twitter
Below are links to the resources and topics mentioned during this episode.
Implement private fields proposal · Issue #9950 · microsoft/TypeScript · GitHub
The future of the “private” keyword · Issue #31670 · microsoft/TypeScript · GitHub