Why Object Nil can't create?












0















Having the error:



Object creation impossible, since member node: Option[(A, MyModule.List[A])] in MyModule.List is not defined






sealed trait List[+A] {
def node: Option[(A, List[A])]
def isEmpty = node.isEmpty
}
abstract class Cons[+A](head: A, tail: List[A]) extends List[A]
object Nil extends List[Nothing]

object List {
def empty[A] = new List[A] { def node = None }
def cons[A](head: A, tail: List[A]) = new List[A] { def node = Some((head, tail)) }

def apply[A](as: A*):List[A] = {
if (as.isEmpty) Nil
else Cons(as.head, apply(as.tail: _*))




In this case, how to implement?
I wonder what functions should be put in trait and what functions should be put in Company Object.








share|improve this question





























    0















    Having the error:



    Object creation impossible, since member node: Option[(A, MyModule.List[A])] in MyModule.List is not defined






    sealed trait List[+A] {
    def node: Option[(A, List[A])]
    def isEmpty = node.isEmpty
    }
    abstract class Cons[+A](head: A, tail: List[A]) extends List[A]
    object Nil extends List[Nothing]

    object List {
    def empty[A] = new List[A] { def node = None }
    def cons[A](head: A, tail: List[A]) = new List[A] { def node = Some((head, tail)) }

    def apply[A](as: A*):List[A] = {
    if (as.isEmpty) Nil
    else Cons(as.head, apply(as.tail: _*))




    In this case, how to implement?
    I wonder what functions should be put in trait and what functions should be put in Company Object.








    share|improve this question



























      0












      0








      0








      Having the error:



      Object creation impossible, since member node: Option[(A, MyModule.List[A])] in MyModule.List is not defined






      sealed trait List[+A] {
      def node: Option[(A, List[A])]
      def isEmpty = node.isEmpty
      }
      abstract class Cons[+A](head: A, tail: List[A]) extends List[A]
      object Nil extends List[Nothing]

      object List {
      def empty[A] = new List[A] { def node = None }
      def cons[A](head: A, tail: List[A]) = new List[A] { def node = Some((head, tail)) }

      def apply[A](as: A*):List[A] = {
      if (as.isEmpty) Nil
      else Cons(as.head, apply(as.tail: _*))




      In this case, how to implement?
      I wonder what functions should be put in trait and what functions should be put in Company Object.








      share|improve this question
















      Having the error:



      Object creation impossible, since member node: Option[(A, MyModule.List[A])] in MyModule.List is not defined






      sealed trait List[+A] {
      def node: Option[(A, List[A])]
      def isEmpty = node.isEmpty
      }
      abstract class Cons[+A](head: A, tail: List[A]) extends List[A]
      object Nil extends List[Nothing]

      object List {
      def empty[A] = new List[A] { def node = None }
      def cons[A](head: A, tail: List[A]) = new List[A] { def node = Some((head, tail)) }

      def apply[A](as: A*):List[A] = {
      if (as.isEmpty) Nil
      else Cons(as.head, apply(as.tail: _*))




      In this case, how to implement?
      I wonder what functions should be put in trait and what functions should be put in Company Object.




      sealed trait List[+A] {
      def node: Option[(A, List[A])]
      def isEmpty = node.isEmpty
      }
      abstract class Cons[+A](head: A, tail: List[A]) extends List[A]
      object Nil extends List[Nothing]

      object List {
      def empty[A] = new List[A] { def node = None }
      def cons[A](head: A, tail: List[A]) = new List[A] { def node = Some((head, tail)) }

      def apply[A](as: A*):List[A] = {
      if (as.isEmpty) Nil
      else Cons(as.head, apply(as.tail: _*))





      sealed trait List[+A] {
      def node: Option[(A, List[A])]
      def isEmpty = node.isEmpty
      }
      abstract class Cons[+A](head: A, tail: List[A]) extends List[A]
      object Nil extends List[Nothing]

      object List {
      def empty[A] = new List[A] { def node = None }
      def cons[A](head: A, tail: List[A]) = new List[A] { def node = Some((head, tail)) }

      def apply[A](as: A*):List[A] = {
      if (as.isEmpty) Nil
      else Cons(as.head, apply(as.tail: _*))






      scala






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 8:57







      Arobt

















      asked Nov 15 '18 at 3:28









      ArobtArobt

      114




      114
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Here is correct implementation:



          sealed trait List[+A] {
          def node: Option[(A, List[A])]

          def isEmpty = node.isEmpty
          }

          case class Cons[+A](head: A, tail: List[A]) extends List[A] {
          override def node: Option[(A, List[A])] = Some((head, tail))
          }

          object Nil extends List[Nothing] {
          override def node: Option[(Nothing, List[Nothing])] = None
          }

          object List {
          def empty[A] = new List[A] {
          def node = None
          }

          def cons[A](head: A, tail: List[A]) = new List[A] {
          def node = Some((head, tail))
          }

          def apply[A](as: A*): List[A] = {
          if (as.isEmpty) Nil
          else Cons(as.head, apply(as.tail: _*))
          }
          }


          I see few problems here:



          1) You have two implementation of cons
          you can implement cons method simpler:



            def cons[A](head: A, tail: List[A]) = Cons(head, tail)


          2) Same with empty



            def empty[A] = Nil





          share|improve this answer
























          • Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

            – Arobt
            Nov 15 '18 at 8:45













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311998%2fwhy-object-nil-cant-create%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Here is correct implementation:



          sealed trait List[+A] {
          def node: Option[(A, List[A])]

          def isEmpty = node.isEmpty
          }

          case class Cons[+A](head: A, tail: List[A]) extends List[A] {
          override def node: Option[(A, List[A])] = Some((head, tail))
          }

          object Nil extends List[Nothing] {
          override def node: Option[(Nothing, List[Nothing])] = None
          }

          object List {
          def empty[A] = new List[A] {
          def node = None
          }

          def cons[A](head: A, tail: List[A]) = new List[A] {
          def node = Some((head, tail))
          }

          def apply[A](as: A*): List[A] = {
          if (as.isEmpty) Nil
          else Cons(as.head, apply(as.tail: _*))
          }
          }


          I see few problems here:



          1) You have two implementation of cons
          you can implement cons method simpler:



            def cons[A](head: A, tail: List[A]) = Cons(head, tail)


          2) Same with empty



            def empty[A] = Nil





          share|improve this answer
























          • Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

            – Arobt
            Nov 15 '18 at 8:45


















          0














          Here is correct implementation:



          sealed trait List[+A] {
          def node: Option[(A, List[A])]

          def isEmpty = node.isEmpty
          }

          case class Cons[+A](head: A, tail: List[A]) extends List[A] {
          override def node: Option[(A, List[A])] = Some((head, tail))
          }

          object Nil extends List[Nothing] {
          override def node: Option[(Nothing, List[Nothing])] = None
          }

          object List {
          def empty[A] = new List[A] {
          def node = None
          }

          def cons[A](head: A, tail: List[A]) = new List[A] {
          def node = Some((head, tail))
          }

          def apply[A](as: A*): List[A] = {
          if (as.isEmpty) Nil
          else Cons(as.head, apply(as.tail: _*))
          }
          }


          I see few problems here:



          1) You have two implementation of cons
          you can implement cons method simpler:



            def cons[A](head: A, tail: List[A]) = Cons(head, tail)


          2) Same with empty



            def empty[A] = Nil





          share|improve this answer
























          • Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

            – Arobt
            Nov 15 '18 at 8:45
















          0












          0








          0







          Here is correct implementation:



          sealed trait List[+A] {
          def node: Option[(A, List[A])]

          def isEmpty = node.isEmpty
          }

          case class Cons[+A](head: A, tail: List[A]) extends List[A] {
          override def node: Option[(A, List[A])] = Some((head, tail))
          }

          object Nil extends List[Nothing] {
          override def node: Option[(Nothing, List[Nothing])] = None
          }

          object List {
          def empty[A] = new List[A] {
          def node = None
          }

          def cons[A](head: A, tail: List[A]) = new List[A] {
          def node = Some((head, tail))
          }

          def apply[A](as: A*): List[A] = {
          if (as.isEmpty) Nil
          else Cons(as.head, apply(as.tail: _*))
          }
          }


          I see few problems here:



          1) You have two implementation of cons
          you can implement cons method simpler:



            def cons[A](head: A, tail: List[A]) = Cons(head, tail)


          2) Same with empty



            def empty[A] = Nil





          share|improve this answer













          Here is correct implementation:



          sealed trait List[+A] {
          def node: Option[(A, List[A])]

          def isEmpty = node.isEmpty
          }

          case class Cons[+A](head: A, tail: List[A]) extends List[A] {
          override def node: Option[(A, List[A])] = Some((head, tail))
          }

          object Nil extends List[Nothing] {
          override def node: Option[(Nothing, List[Nothing])] = None
          }

          object List {
          def empty[A] = new List[A] {
          def node = None
          }

          def cons[A](head: A, tail: List[A]) = new List[A] {
          def node = Some((head, tail))
          }

          def apply[A](as: A*): List[A] = {
          if (as.isEmpty) Nil
          else Cons(as.head, apply(as.tail: _*))
          }
          }


          I see few problems here:



          1) You have two implementation of cons
          you can implement cons method simpler:



            def cons[A](head: A, tail: List[A]) = Cons(head, tail)


          2) Same with empty



            def empty[A] = Nil






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 15 '18 at 3:46









          talextalex

          10.6k1547




          10.6k1547













          • Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

            – Arobt
            Nov 15 '18 at 8:45





















          • Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

            – Arobt
            Nov 15 '18 at 8:45



















          Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

          – Arobt
          Nov 15 '18 at 8:45







          Yes, Cons and Empty implementations are duplicated. In the object List, no new List is needed, only the new Cons and Nil are needed.Just like you added.

          – Arobt
          Nov 15 '18 at 8:45




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311998%2fwhy-object-nil-cant-create%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          Tangent Lines Diagram Along Smooth Curve

          Yusuf al-Mu'taman ibn Hud

          Zucchini