Readonly<T> miss all internal symbol keys #37182

Activity

1. RyanCavanaugh commented on Mar 4, 2020

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Mar 4, 2020

   Last edited by RyanCavanaugh

   Member

   More actions

   Anders Hejlsberg (@ahejlsberg) wasn't this scenario the use case for #23592 ?
2. ahejlsberg commented on Mar 4, 2020

   

   Anders Hejlsberg (ahejlsberg)

   on Mar 4, 2020

   Member

   More actions

   wasn't this scenario the use case for #23592 ?

   Yes, except we have always excluded "well known symbols" from keyof. The fix really is to get rid of the well known symbol concept and just treat them all as unique symbols.

   👀React with 👀1Reacted by Justin Grant
3. ahejlsberg commented on Mar 4, 2020

   

   Anders Hejlsberg (ahejlsberg)

   on Mar 4, 2020

   Member

   More actions

   See #24738.
4. Ryan Cavanaugh (RyanCavanaugh)

   added

   Experimentation NeededSomeone needs to try this out to see what happensSomeone needs to try this out to see what happens

   on Mar 11, 2020
5. Ryan Cavanaugh (RyanCavanaugh)

   added this to the Backlog milestone on Mar 11, 2020
6. PSeitz commented on Mar 12, 2020

   

   PSeitz

   on Mar 12, 2020

   More actions

   This blocks converting Readonly Sets to Arrays

   const mySet: Readonly<Set<string>> = new Set();
   const myArr = [...mySet]; // Type 'Readonly<Set<string>>' must have a '[Symbol.iterator]()' method that returns an iterator.
   

   👍React with 👍3Reacted by Justin Grant, 翠 and DzmitryFil
7. Wesley Wigham (weswigham)

   closed this as completedin #42543on Feb 22, 2021