We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
Loading...
  1. Practice
  2. Functional Programming
  3. Introduction
  4. Array Of N Elements
  5. Discussions

Array Of N Elements

Sort 82 Discussions, By:

votes

  • avi_mathur + 2 comments

    In Scala the line 

    println ( list + "\n" )

    must be removed.

    • xavier_guihot + 0 comments

      yes, since the result is then outputed twice, making the tests fail

    • civilizeddev + 0 comments

      Yes, but you can change the return type of the function f to String instead.

  • dillonredding + 5 comments

    I'm getting the following compile message in Scala, regardless of how I write it:

    warning: there was one deprecation warning; re-run with -deprecation for details
one warning found
    • hpedrorodrigues + 0 comments

      I had the same message.

    • saberwang + 0 comments

      Me, too. I think it's a bug in python scripts that run on Server . Foget my Bad English

    • saberwang + 0 comments

      def f(num:Int) : List[Int] = if(num==0) List() else num::f(num-1)

      I'm sure that's right

    • AllisonP + 2 comments

      Sorry about this, Scala is fixed now.

      • sethia_arun + 0 comments

        I am getting this error , I don't see any issue here in scala code

        val list:List[Int]=(0 until num).toList

        It will give f(2) will be List(0,1,2)

        warning: there was one deprecation warning; re-run with -deprecation for details one warning found

      • sbacarob + 1 comment

        Could you check for Elixir? Test case #1 and Test case #2 have a wrong expected output

        • liborio7 + 1 comment

          I had the same problem with Test case #1 and #2. In my case the problem was the IO.inspect function. I solved it limiting to infinity the output: IO.inspect(list, limit: :infinity)

          • rossiheron + 0 comments

            Thanks, it worked for me.

    • LuisLC + 0 comments

      Issue is with the readInt method.I get the following when running the same program locally, using the the -deprecation tag:

      /home/lcampos/Development/learn-scala/Solution.scala:7: warning: method readInt in trait DeprecatedPredef is deprecated (since 2.11.0): use the method in `scala.io.StdIn`
  println(f(readInt))

      Ok, so the last line of code should be:

      println(f(scala.io.StdIn.readInt))

  • u_suke_goto + 2 comments

    seems broken on elixir as well

    • mobileka + 0 comments

      Confirmed.

      It passes when I run the code, but fails all the tests when I submit it.

    • AllisonP + 2 comments

      I'm able to pass in Elixir. Do you want to try it again and see if you're still having an issue? Make sure you're printing a space/comma/semicolon-separated list.

      • mobileka + 1 comment

        Looks like test cases #1 and #2 are still broken. These cases expect an integer number as an output but it has to be a list instead.

        • HuShifang + 1 comment

          Confirmed this -- my code passes all the test cases but #1 and #2, and when I "purchase" test case #2, it indicates that the input and output should both be the integer X -- not a list of length X.

          • rossiheron + 0 comments

            Still broken

      • idabmat + 0 comments

        Sorry something still seems weird. Testcase 1 passes when "running" the code, but then it fails when "submitting" it.

  • petertheking + 3 comments

    Is the checker broken for clojure? Input is 10, expected output is 10?

    • davcamer + 0 comments

      I believe expected output is a list of ten elements. This is unclear in the problem statement, but a list of ten elements satisfies the checker for Scala.

    • non_dmitriy + 1 comment

      It's not broken. More than that, there's a one-word solution on Clojure ;D

      • petertheking + 0 comments

        Thanks all. I solved it the first time using one of the one-word solutions in Clojure the first time around, although I think it defeats the spirit of some of these questions.

    • AllisonP + 1 comment

      Try it again, I've made some corrections to the checker.

      • dsncode + 0 comments

        it does stil enforce me to print List as object. ex: List(1,2,3,4..) and there is no way to print like is required [1,2,3,4,5...]

  • itissera + 5 comments

    Seems that there is a problem in the checker for Scala. Same issue reported by other users. The output checked is not what I get in my scala REPL.

    • sidproquoAsked to answer + 0 comments

      Agreed. I just checked with my previously submitted code (which had cleared all test cases). The same code is failing now. It's broken, yeah.

    • krauszraphael + 1 comment

      Me too!

      Argh... I've done this exercise 5 times in 5 different ways - all marked wrong, but all right in my REPL.

      • bi_myname + 0 comments

        same

    • tjano + 0 comments

      Looks like noone reads our complains :(

    • gciuloaica + 0 comments

      it is still broken for both run code and submit, for scala

    • AllisonP + 1 comment

      This is fixed. Sorry!

      • gciuloaica + 0 comments

        yep. it works. Thanks

  • rmrhr + 0 comments

    If you are using Elixir and IO.inspect to output the list, make sure to add limit: :infinity in the options.
    http://elixir-lang.org/docs/stable/elixir/Inspect.Opts.html

  • adamlabbe + 1 comment

    The test runner appears broken, anything solution I try results in this Python error:

    Traceback (most recent call last): File "/custom-ztciEr8Zbx3aAXhveWH4/solution.py", line 94, in score, testcase_status = process(data) File "/custom-ztciEr8Zbx3aAXhveWH4/solution.py", line 56, in process is_code_works, scores, testcase_statuses = check_inputs(testcase_input, testcase_output, user_output) File "/custom-ztciEr8Zbx3aAXhveWH4/solution.py", line 46, in check_inputs raise("check") TypeError: exceptions must be old-style classes or derived from BaseException, not str

    • savanni_dgerinel + 0 comments

      Seeing this, too. I am providing a correct Haskell solution (tested in the REPL), and it is not actually even running my solution.

  • balintant + 0 comments

    Haskell

    fn n = [1..n]

  • nuno_mvrodrigue1 + 3 comments

    Admins , the tests are not working for haskell , i test the same function here and on ghc and here it gives a wrong output

    • dape + 1 comment

      Not working for me either. Only the length of the list returned by the function is sent to output, and since main can't be overwritten, it's impossible.

      • hololeap + 0 comments

        Same observations here.

    • hololeap + 0 comments
      [deleted]
    • AllisonP + 1 comment

      I'm wasn't having any issues passing with Haskell, but I made changes to the checker and code stubs. Try resubmitting and see if it helps.

      • mnoronha + 1 comment

        For some reason, the haskell checker rejects [1..n], but accepts [1..(n)]

        • brynmurrell97 + 0 comments

          Not for me

          f n = [1..n]

          worked fine for me

  • barciella + 0 comments

    This is my solution in clojure: (fn[n] (range n))

Load more conversations