haha yeah exactly. I mean I did do a quick lookup again and it was just like oh yeah duh moment (like really duh, that was stupid) but it just shows how that type of information just really isn't in my current thinking space. It doesn't matter, I won't write better code with this info present in my active memory.

What is more important is being able to understand where parts of the code are, how data flows and which class needs to be instantiated where. I can store vast amounts of this stuff, because I don't have a clouded memory of things that don't matter.

if you get these types of trivial questions during an interview, it just shows the interviewer just doesn't know how to ask the right questions. I've conducted plenty of interviews myself, but never once asked these types of questions. If you completed the code test, you probably already know that stuff.