Description

Ryan Cavanaugh (RyanCavanaugh)

opened on Oct 1, 2018

Issue body actions

• decorator/export ordering update
  • No progress per se
• JSIDL
  • Possible thing for us to parse for dom lib generation
  • Why not TS?
    • Why not Flow?
    • Why not Zoidberg?
    • Some members are salty about interface keyword being stomped by TS
• Dynamic modules has been cut back to the minimum thing needed
• Denoting an expression as a literal
  • e.g. suggestion: explicit "tuple" syntax #16656
  • Option: Add new syntax
    • All of it is fairly gross
  • Option: Push const initializers and parameter values closer to the non-widening area
  • What about using control flow analysis to allow for initialized discriminated unions to be correctly identified?
  • The intent of some code is really unclear
  • What should foo<T>(x: T): T do with e.g. { kind: "bar"} ? Return { kind: "bar" } or { kind: string } ? Arguable both ways
  • Anders tried inferring a tuple for all arrays of more than 1 element... broke lots of stuff
  • What about detecting local mutations and choosing a non-widened type when there are none?
    • Breaks down in some cases (e.g. aliasing, which we're already highly unsound to)
    • Would be rather wrong in closure situations
  • konst
  • :sad shrug:
• Infer array rest as tuple if possible #26070 Infer rest as tuple in binding patterns
  • Certainly fine/correct in zero-order case
  • 👍
• Resolve tsconfig.json extends path using node_modules resolution logic #18865 Use node module resolution for tsconfig extends files
  • 👍
  • Add showconfig too
  • What about tsconfig.js?
    • Nooooooooooooooooooooooooooooo
• ADTs with inheritance #20144 / Allow any key type as an index signature parameter type #26797 Regex types and index signatures, the peanut butter and chocolate of object types
  • Next time!

Reacted by Daniel Rosenwasser and David Edmondson

Activity

1. Ryan Cavanaugh (RyanCavanaugh)

   added

   Design NotesNotes from our design meetingsNotes from our design meetings

   on Oct 1, 2018
2. shobhitg commented on Oct 7, 2018

   

   Shobhit Gupta (shobhitg)

   on Oct 7, 2018

   More actions

   Ryan Cavanaugh (@RyanCavanaugh) Are these design meeting open (or recorded)?
   It would be very illuminating to be able to see a recording of these design meetings.
3. RyanCavanaugh commented on Oct 8, 2018

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Oct 8, 2018

   MemberAuthor

   More actions

   Shobhit Gupta (@shobhitg) nope. I don't think a recording is something we could do for a variety of reasons, but I think some other forum to elaborate more on certain decisions would be interesting
4. Ryan Cavanaugh (RyanCavanaugh)

   closed this as completedon Oct 8, 2018
5. rozzzly commented on Oct 27, 2018

   

   Patrick Lienau (rozzzly)

   on Oct 27, 2018

   More actions

   Shobhit Gupta (@shobhitg) nope. I don't think a recording is something we could do for a variety of reasons, but I think some other forum to elaborate more on certain decisions would be interesting

   I have two assume two of the "reasons" are:

   • Microsoft HR/legal would want increased level of oversight --> slow speed of iteration

   • "plz don't turn casual yet productive brainstorming into tedious public hearing"

   I can understand that, but it would be really cool if the TS team could occasionally do a live stream where community has chatroom to converse with TS team. Or even just a podcast type thing.

   It certainly wouldn't be ever week, but maybe 3-4 times a year like for an hour?

   Just discuss what you're working on, ask for some feedback/answer some questions. Then talk about upcoming plans. Ask the chat what it thinks should be higher priority,etc.

   I think that because community attendance to a live event poses a "higher bar to entry" compared to posting an issue on GH, that only community members who are truly interested and likely have actual understanding of the topics being discussed would make the commitment to attend. I think there's the potential for some high-level discourse to occur.

   Reacted by Daniel Rosenwasser and Andrei

Issue actions