288 karma · joined June 14, 2018
(1..100).map { |i| i.modulo(15).zero? && "FizzBuzz" || i.modulo(3).zero? && "Fizz" || i.modulo(5).zero? && "Buzz" || i }Dart? Elm? Clojurescript? Objective-J?
One interesting thing about the my phone is I managed to crack the screen on the 3 iPhones I had before, sometimes multiple times. I've put this one through hell and back and it just keeps going. I wonder if the build quality (not just features and performance) has been a factor in slowing upgrades...
There is nothing addressed here that can't be solved with composition. This seems like an odd step for an aspiring functional language to take...
What are some of the other languages that interpret "private" as never exposing the existence of that field to a public consumer? Most languages I've used don't expose the _value_ of the field...
> Having a private field named x must not prevent there from being a public field named x, so accessing a private field can't just be a normal lookup.
Why do classes support public/private fields of the same name in the first place? This seems fraught by nature?
Your comment doesn't deserve downvotes.
In the short term I suspect they won't strike at all. NYC and DC rents are expensive.
It's really not that uncommon for people outside of major cities to own their home?
When I needed to make food or just run away from the PC, I would get a P90 and rush the corridor. It was suicide but you could absolutely wreak havoc with the high rate of fire.
The L train?
Unless it was on the weekend when there are a multitude of service interruptions and station closures.
When it happens I hope you aren't swept up since we are going to need people who have the answers to everything.