8 Matching Annotations
  1. Feb 2024
  2. Dec 2023
    1. well I'll start with two extremely optimistic points
      • for: answer to above question

      • answer : two answers

        • first, the elite have the majority of
          • wealth
          • control of setting policies
          • control of the media
          • and they work really hard at controlling policy and media
          • and the people
            • hate the system
            • generally hate them
        • second, social tipping points occur. Something happened in over place, then it spreads to other places
  3. Mar 2021
  4. Aug 2020
  5. Nov 2019
  6. Oct 2019
    1. Let's make the example even easier. function convertDate<T extends string | undefined>(isoDate?: string): T { return undefined } 'undefined' is assignable to the constraint of type 'T' Means: What you return in the function (undefined), matches the constraints of your generic type parameter T (extends string | undefined). , but 'T' could be instantiated with a different subtype of constraint 'string | undefined'. Means: TypeScript does not consider that as safe. What if you defined your function like this at compile time: // expects string return type according to generics // but you return undefined in function body const res = convertDate<string>("2019-08-16T16:48:33Z") Then according to your signature, you expect the return type to be string. But at runtime that is not the case! This discrepancy that T can be instantiated with a different subtype (here string) than you return in the function (undefined) is expressed with the TypeScript error.