More human readable `Memory used` output when running `tsc`

[hamirmahal]

🔍 Search Terms

human readable Memory used diagnostics formatting

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

It'd be nice if the Memory used output when running tsc with the --diagnostics flag was more human readable.

📃 Motivating Example

242380K is a bit harder to wrap my mind around. I think a more human readable Memory used would be a nice improvement.

> tsc --diagnostics --noEmit

Files:              322
Lines:           142602
Identifiers:     126674
Symbols:         158347
Types:            70954
Instantiations:   79936
Memory used:    242380K
I/O read:         0.02s
I/O write:        0.00s
Parse time:       0.51s
Bind time:        0.19s
Check time:       1.79s
Emit time:        0.00s
Total time:       2.49s

💻 Use Cases

This would make it easier to understand tsc's memory usage.

[RyanCavanaugh]

Someone might be parsing this output, and for the most part the order of magnitude on these numbers is apparent to anyone who needs to care in the first place.

[typescript-bot]

This issue has been marked as "Declined" and has seen no recent activity. It has been automatically closed for house-keeping purposes.

[SirzBenjie]

Someone might be parsing this output, and for the most part the order of magnitude on these numbers is apparent to anyone who needs to care in the first place.

The fact that a single member of the TypeScript team can unilaterally reject solid ideas with absolutely no recourse, discussion with the community, or even consideration just by pulling the "but my backwards compatibility" excuse is quite discouraging.
@RyanCavanaugh Who are you to continually gatekeep this open source project based solely on your discretion?

TypeScript needs a steering community. This is getting absolutely ridiculous.