Ruby 2.6 - Hackdot

Re:Ruby 2.6 by ken on Monday December 24, 2018 @01:58PM (#18753652)

There's got to be more to it than "has / doesn't have nil". Lisp has nil, and I rarely if ever see an analogous error there, or even a type error.

I have a hunch that single/static dispatch is what tends to cause more problems than merely the presence of nil. It's not nil, but how you use it.

[ Parent | on HN ]

Re:Ruby 2.6 by akjha on Tuesday December 25, 2018 @03:10AM (#18756523)

"It's not nil, but how you use it."

Can you elaborate on how multi-dispatch reduces the issue of nil/null?

I also use static type (typescript) to prevent issues with nil and would like to know how I can achieve the same in a dynamic language.

[ Parent | on HN ]

Re:Ruby 2.6 by jashmatthews on Wednesday December 26, 2018 @05:25AM (#18761519)

You can prevent nil errors using contracts like in Eiffel and Clojure.

[ Parent | on HN ]