proposal-record-tuple #39831

Activity

1. Ryan Cavanaugh (RyanCavanaugh)

   added

   SuggestionAn idea for TypeScriptAn idea for TypeScript

   Waiting for TC39Unactionable until TC39 reaches some conclusionUnactionable until TC39 reaches some conclusion

   on Jul 30, 2020
2. RyanCavanaugh commented on Jul 30, 2020

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Jul 30, 2020

   Member

   More actions

   FYI we're tracking these as part of our TC39 committee attendance, so there's not really a need to have TS issues for every stage 2 proposal - we don't want to fracture the discussion.

   👍React with 👍4Reacted by Aleksey Levenstein, Peter Hozák, Taro and Anton Mikhailov
3. armanozak commented on Aug 2, 2020

   

   Levent Arman Özak (armanozak)

   on Aug 2, 2020

   More actions

   Hi Ryan Cavanaugh (@RyanCavanaugh),

   I understand, but also share Wenlu Wang (@Kingwl)'s concern. This is not a regular TC39 proposal. It introduces a global constructor which may cause a breaking change in TypeScript. It would be kind of you if you could share TypeScript's stance about the naming. Does it look like Record is going to be the eventual name for that constructor or is it still subject to change?
4. Kingwl commented on Aug 2, 2020

   

   Wenlu Wang (Kingwl)

   on Aug 2, 2020

   Last edited by Kingwl

   ContributorAuthor

   More actions

   Levent Arman Özak (@armanozak) I think it's might be ok. The ctor 'Record' is value and Record<> is type. TypeScript is work fine with this case. As the result, the type of record might be 'record', the lower case. Like number and Number, string and String.
5. Kingwl commented on Aug 2, 2020

   

   Wenlu Wang (Kingwl)

   on Aug 2, 2020

   ContributorAuthor

   More actions

   But i'm not sure the other case. eg: Array ctor has type parameter, But seems Record cannot.
6. armanozak commented on Aug 2, 2020

   

   Levent Arman Özak (armanozak)

   on Aug 2, 2020

   More actions

   Hi Wenlu Wang (@Kingwl),

   The type is record and I am not worried about that. I am not even worried about the wrapper object type (like String, Number, and Boolean), because it is stated here that there will be no wrapper object instantiation.

   However, TypeScript Record is not really a match for the proposed Record and that would cause confusion, don't you agree?

   👍React with 👍5Reacted by Wenlu Wang, matt-senseye, Lou Cyx, Matthew Francis Brunetti and Kris Kalavantavanich
7. Jack-Works commented on Aug 23, 2021

   

   Jack Works (Jack-Works)

   on Aug 23, 2021

   Contributor

   More actions

   Working on this #45546

   👍React with 👍2Reacted by Linz and lin72h

   🎉React with 🎉3Reacted by Linus Unnebäck, lin72h and debby
8. gioragutt commented on Oct 25, 2021

   

   Giora Guttsait (gioragutt)

   on Oct 25, 2021

   More actions

   Levent Arman Özak (@armanozak) have there been cases where there was such a big possible breaking change before?

   How is TypeScript supposed to handle such a change? Hypothetically speaking, if it'll actually happen, what would be the protocol for that? Major change and GL codemodding the broken changes?