• mozingo
    link
    fedilink
    English
    291 year ago

    This sure looks like C#. I use typeof every once in a while when I want to check that the type of a reference is a specific type and not a parent or derived type. But yea, really not that often.

    • m_r_butts
      link
      fedilink
      3
      edit-2
      1 year ago

      It can’t be actual C#, but it does look like it.

      If you declare a class Pie<T>{} then attempt to call typeof(Pie<T>) or typeof(T) it won’t even build because you failed to specify what type T is. typeof(Pie<object>) would work but that just returns “Pie1[System.Object]”.

      • @[email protected]
        link
        fedilink
        English
        31 year ago

        I have used typeof(T) inside the generic class, so fx a function inside the class Pie where T can be refered. But out of context, if you were to call typeof(T) inside Program.cs’s main function, it would not work.

        • m_r_butts
          link
          fedilink
          21 year ago

          Yeah, but to do that you’d need an instantiated instance of the Pie class, which would answer in the context of the generic type parameter, not the whole Pie class.

          This is too funny. Everyone here, me included, is profoundly overthinking this, lol.

      • @[email protected]
        link
        fedilink
        11 year ago

        Typescript! Though it’s less useful, since the Typescript types aren’t available at runtime, so you’ll just get object for non-primitive values.

      • @[email protected]
        link
        fedilink
        11 year ago

        Probably because Java and C# take much inspiration from C++. They aren’t called “C-based” languages for nothing 😉