uhmm. I personally prefer to write code that solves the problem I'm trying to solve then worry about how the style fits and what problems I had/didn't have with it, especially if its just a throw away script
why are you forcing this to one line? is there some kind of quota on newlines?
i mean do you have receive_direct_message_alerts and receive_direct_message_alerts=
because it looks like you are calling two different implementations and wondering why each has its own return value
but I only see one implementation, receive_direct_message_alerts=
okay... what I'm saying is you could be calling "methodA" and it gives you false. later you call "methodB" and it gives you true, then you again call "methodA" and it gives you false again, which is expected...
receive_direct_message_alerts and receive_direct_message_alerts= aren't the same method , they could be defined totally different
I was recently playing around with using sentinel style values to indicate intent rather than nil/empty and one of the things I found cumbersome was when you use a value like :no_value instead of leaving it nil, that operations like .any? treat :no_value as true, but nil as false
havenwood: if I understand what hes said correctly its basically "Solving this is a language problem and none of them have great solutions here are some things I'm poking at or proposing"