selfie, ec
@mavica So, pretty! *swoon* 
NASA brings Voyager 2 fully back online, 11.5 billion miles from Earth:
https://www.inverse.com/science/nasa-brings-voyager-2-fully-back-online-11.5-billion-miles-from-earth
hacking over a connection with a ping latency of 122,400,000 ms.
@kinsey It's also kind of a go idiom what nil values *should* be valid if possible.
So, I guess that while a nil *os.File is not a valid open file its a "valid" *os.File, in the sense that you can call all the methods and expect to get an error in return instead of panicking. 🤷♀️
@kinsey I'll return an error, yea, but you can just ignore the return value in that case.
@kinsey If os.Open (or os.Create) returns an error then the file pointer returned will be nil. So defer file.Close() would be... not ok.. wait? No, you can call Close() on a nil *os.File!
TIL
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess
Avatar by mavica