• mozingo@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    1
    ·
    11 months 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@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      11 months 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]”.

      • tonur@feddit.dk
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 months 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@kbin.social
          link
          fedilink
          arrow-up
          2
          ·
          11 months 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.