Dev/nich/point equals null bug

[NishantChandrashekhar]

What type of PR is this? (check all applicable)

• [ ] ♻️ Refactor
• [ ] ✨ Feature
• [x ] 🐛 Bug Fix
• [ ] 👷 Optimization
• [ ] 📝 Documentation Update
• [ ] 🔖 Release
• [ ] 🚩 Other

Description

Previously, the equals and the == operator of the Point3 didn't handle the null input case, ie if one (or both) of the inputs were null then the function would throw an error. I have modified the function to return false when either of the inputs is null or if both the inputs are null (the second scenario is what I have observed when I compared two string variables having null values).

This PR Fixes #417 .

Added tests?

• [x] 👍 yes
• [ ] 🙅 no, because they aren't needed
• [ ] 🙋 no, because I need help

Added to documentation?

• [ ] 📓 docs
• [x ] 🙅 no documentation needed

[d3ssy]

Thanks @NishantChandrashekhar! Looks good to go