Sen

i feel like C# has never been able to Generic as hard as i want, i wanna do shit like

public abstract class Something<T> where T : SomethingElse {
    public abstract T GetSomethingElse();
}

public class ThingProducer {
    // This is the thing I can't do.
    private List<Something<?>> things; 

    public IEnumerable<SomethingElse> GetOtherThings() {
        return things.Select(GetSomethingElse);
    }
}

i can instead do this, but i don't like it because it doesn't provide the same type restriction on child classes of Something

public abstract class Something {
    public abstract SomethingElse GetSomethingElse();
}

public class ThingProducer {
    // This is now Legal.
    private List<Something> things; 

    public IEnumerable<SomethingElse> GetOtherThings() {
        return things.Select(GetSomethingElse);
    }
}

This morning I started up the new Pokemon, and like the past couple generations it uses a "what do you look like" prompt in place of the old "Are you a Boy or a Girl?"

A lot of games are going this route, and while the body types shown are still a restrictive normative "masculine"/"feminine", overall I view it as a small positive step in the right direction to support trans, non-binary, and genderqueer folks of all sorts. And so it's pretty disappointing how quickly the game undermines that by immediately and transparently using "Look" selection as a full binary gender determination - I picked the "feminine" Look and within a few minutes I was getting addressed with "Miss", "daughter", "she/her", etc.

Games like Pokemon are stuck in a bizarre half-state of seemingly wanting to present a more inclusive experience for folks while also totally not knowing how to deliver on that in gameplay and writing.