By inheriting from a class, you are implicitly accepting responsibility for all of the messages that the superclass sends on your behalf, not just the messages that your class can receive.
A perfect implementation of the wrong specification is worthless. By the same principle a beautifully crafted library with no documentation is also damn near worthless.
Hey everyone, thanks for your patience with freeCodeCamp's overloaded servers. It has been a looooong week.
Here's what happened and what we've learned from the experience.
https://t.co/7RsMogom6U
I recently learned about requireContext() in Fragments - it's super awesome and useful. If there's no context available, you might be doing something wrong and it can make more sense to crash, which requireContext() enables without having a nullable type!
The compilers and tools are built like any other professional software product: by breaking the problem down, writing one line of code at a time, and then testing the heck out of the resulting program.
Day 6 #100DaysOfCode Being a parent and with fulltime job it is hard enough to maintain the continuous streak. Took a 10days break and resuming now. Update created a lexical analyser that can recognize one symbol and that is "=>" @_100DaysOfCode
Day 5 #100DaysOfCode Bit relaxing, Just doodling my own questions from day 4 about Lexical analyer @_100DaysOfCode#NeedMotivation Proud that I took the path which is not so common BuildingACompiler!!