Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object oriented language (ALGOL W). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn't resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years.

      -Sir C. A. R. Hoare

      Get rid of nulls services? Possibly with something like this?

       
      public interface Optional<T> extends Provider<T> {
        boolean isPresent();
      }
      
      public class TestService {
        @Inject
        Optional<MyService> myService;
      
        public void doSomething() {
          if(myService.isPresent()) {
             MyService service = myService.get();
             //do something
          }
      }
      

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            jwells
            Reporter:
            saden
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: