Activity

1. Ryan Cavanaugh (RyanCavanaugh)

   added

   BugA bug in TypeScriptA bug in TypeScript

   on Jul 8, 2021
2. Ryan Cavanaugh (RyanCavanaugh)

   added this to the TypeScript 4.5.0 milestone on Jul 8, 2021
3. Ryan Cavanaugh (RyanCavanaugh)

   added

   Help WantedYou can do thisYou can do this

   on Jul 8, 2021
4. TypeScript Bot (typescript-bot)

   added

   Fix AvailableA PR has been opened for this issueA PR has been opened for this issue

   on Jul 10, 2021
5. tchetwin commented on Jul 14, 2021

   

   Thomas Chetwin (tchetwin)

   on Jul 14, 2021

   More actions

   I accidentally duplicated this in #45023. Carrying over a point from there:

   "Side effects" in initialization of static fields already behaved similarly (since ~forever):

   let c: number;
   class C {
     static f = (c = 10);
   }
   c; // Variable 'c' is used before being assigned.(2454)
6. fwienber commented on Sep 13, 2021

   

   Frank Wienberg (fwienber)

   on Sep 13, 2021

   More actions

   What about this even simpler case:

   class Foo {
       static {
           Foo.doSomething(); // Error: "Property 'doSomething' is used before its initialization.(2729)"
       }
   
       // this is how Babel rewrites the above:
       static #_ = (() => {
           Foo.doSomething(); // Now, the forward reference is allowed!
       })();
   
       static doSomething(): void {
          console.log("gotcha!");
       }
   }
   

   This code on TypeScript Playground
   Are class static blocks supposed to be more strict in this regard?
   The Babel rewrite for class static blocks is to define an unused, #private static variable whose initializer is a self-evaluating arrow function. Using the rewrite, TypeScript does not complain about the forward reference.
   At runtime, both variants work.
   It seems to me that the TypeScript error should not be raised in this case.
   Is this the same problem as above or should I create a separate issue?
7. Zzzen commented on Sep 14, 2021

   

   Zzzen (Zzzen)

   on Sep 14, 2021

   Contributor

   More actions

   I believe that's a separate issue.

   ❤️React with ❤️1Reacted by Frank Wienberg
8. Ryan Cavanaugh (RyanCavanaugh)

   added

   RescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone

   on Dec 15, 2021
9. Ryan Cavanaugh (RyanCavanaugh)

   modified the milestones: TypeScript 4.5.0, TypeScript 4.6.0 on Dec 15, 2021
10. Ryan Cavanaugh (RyanCavanaugh)

    modified the milestones: TypeScript 4.6.0, TypeScript 4.6.1 on Feb 3, 2022
11. Ron Buckton (rbuckton)

    closed this as completedin #44969on Mar 23, 2022
12. microsoft

    locked as resolved and limited conversation to collaborators on Oct 21, 2025