Yeah, I think that == suits better for conditionals or for Object construction I guess, but to organize methods reducing the number of lines of code, plus the validation implicit makes Method(string s!) better than Method(string? s)...//string validation
But I'm certainly need test this more clearly 😄
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, I think that == suits better for conditionals or for Object construction I guess, but to organize methods reducing the number of lines of code, plus the validation implicit makes
Method(string s!) better than Method(string? s)...//string validationBut I'm certainly need test this more clearly 😄