Use the readonly modifier on properties or Readonly<T> utility type to prevent reassignment.
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Context (tags): readonly, types
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "how-do-you-make-properties-readonly-in-typescrip"
function explain() {
// Start from the core idea:
// Use the readonly modifier on properties or Readonly<T> utility type to prevent reassignmen
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).