Description

Ryan Cavanaugh (RyanCavanaugh)

opened on Jun 8, 2016

Issue body actions

• Suggestion: Only create global variable for module if something tangible is exported #8668 Only create global variable for module if something tangible is exported
• Bug: Accessing private statics in a class via its derived class is allowed #8624 Accessing private statics in a class via its derived class is allowed
• Should awaiting a non-Promise value be an error? #8310 Should awaiting a non-Promise value be an error?
• Do not rename imports from ambient modules #8227 Do not rename imports from ambient modules
• Suggestion: stricter operators #7989 Stricter binary operators
• Make exported consts better minifiable #7565 Make exported consts better minifiable
• make the strict equality comparison operator a typeguard for string literal types #7447 make the strict equality comparison operator a typeguard for string literal types
• Consider re-ordering Array#reduce overloads in lib.d.ts #7014 Consider re-ordering Array#reduce overloads in lib.d.ts
• Support override keyword on class methods #2000 Support override keyword on class methods
• No compile error thrown when this referenced before call to super completes #8060 Re-order emit of var _this = this when arrow func appears in super call
• Allow ArrayLike as a spread source #7596 Allow ArayLike as a spread source (and figure out emit semantics)
• Extended type parameters don't work as constraints with overloads #7378 Extended type parameters don't work as constraints with overloads

Activity

1. Ryan Cavanaugh (RyanCavanaugh)

   added

   Design NotesNotes from our design meetingsNotes from our design meetings

   on Jun 8, 2016
2. RyanCavanaugh commented on Jun 8, 2016

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Jun 8, 2016

   MemberAuthor

   More actions

   • Suggestion: Only create global variable for module if something tangible is exported #8668 Only create global variable for module if something tangible is exported
     • Why not use an IIFE?
       • Qualification
     • Does future extension matter?
       • Don't see why
     • Too complex; workaround exists
   • Bug: Accessing private statics in a class via its derived class is allowed #8624 Accessing private statics in a class via its derived class is allowed
     • Agree
     • Breaking change
   • Should awaiting a non-Promise value be an error? #8310 Should awaiting a non-Promise value be an error?
     • No
     • It's sometimes useful
     • Also OK because consistency with union types
       • And generics
   • Do not rename imports from ambient modules #8227 Do not rename imports from ambient modules
     • Agree
     • User must write alias and then rename
     • Fix is to restrict syntactic forms of rename invocation sites
   • Suggestion: stricter operators #7989 Stricter binary operators
     • Clearly suspect for numeric/bitwise operands; make these an error
     • string + [whatever] is still OK, or at least less clear
     • What about add an option that flags coercion #7746?
       • Proposal: Disallow implicit truthiness checks for non-null types in strictNullChecks mode?
         • What constitutes a truthiness operand?
           • if and other control flow expressions, and the left operand of || / &&, operand of !
       • Other behavior listed here is idiomatic
   • Make exported consts better minifiable #7565 Make exported consts better minifiable
     • 👍 and wait for new emitter to land
   • make the strict equality comparison operator a typeguard for string literal types #7447 make the strict equality comparison operator a typeguard for string literal types
     • Breaking change: This would (badly) restrict the domain of variables whose type was inferred from value
     • 👎 without use cases to justify break
   • Consider re-ordering Array#reduce overloads in lib.d.ts #7014 Consider re-ordering Array#reduce overloads in lib.d.ts
     • Try it and see wha thappens
   • Support override keyword on class methods #2000 Support override keyword on class methods
     • What about override properties?
       • Sure, no reason not to
     • --noImplicitOverride means what you think it does
       • Should this apply to declaration files?
         • Argument for yes: correctness for the same reason
         • Argument for no: convenience, no need to mess with declaration emitter
         • If no: Declaration emitter will need to emit override modifier (same way any works) if one was not present explicitly
         • Decision: Not enforced
     • Nothing for interface implementations at this time
     • No special type behavior at this time
     • Accepting PRs
   • No compile error thrown when this referenced before call to super completes #8060 Re-order emit of var _this = this when arrow func appears in super call
     • 👍, Community
   • Extended type parameters don't work as constraints with overloads #7378 Extended type parameters don't work as constraints with overloads
     • Overload/implementation signature checking is already pretty bad anyway
     • Too Complex

   Out of time

   • Allow ArrayLike as a spread source #7596 Allow ArrayLike as a spread source (and figure out emit semantics)
3. RyanCavanaugh commented on Jun 9, 2016

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Jun 9, 2016

   MemberAuthor

   More actions

   #7746 (use of known-true/known-false values in truthiness positions) moved to #9041
4. Ryan Cavanaugh (RyanCavanaugh)

   closed this as completedon Jun 9, 2016
5. microsoft

   locked and limited conversation to collaborators on Jun 19, 2018

Issue actions