Ad
  • Custom User Avatar
  • Default User Avatar

    you are training on a long-outdated version of the sample tests.

  • Custom User Avatar

    (python)

    • The sample tests require a function named pareto and the expected output is a list of list

    • The submissions tests (also in the description) require a function named pareto_front whereas the expected output is a set of tuples.

    • Th domination criteria is not explicit Wiki:

      An allocation {x_{1},\dots ,x_{n}}, where x_{i} in R^{k} for all i, is Pareto-optimal if there is no other feasible allocation
      {x_{1}',... ,x_{n}'} where, for utility function u_{i} for each agent i, u_{i}(x_{i}') >= u_{i}(x_{i}) for all i in {1, ... ,n} with
      u_{i}(x_{i}') > u_{i}(x_{i}) for some i

  • Custom User Avatar

    approved. author is inactive.

  • Custom User Avatar

    JS translation

    this translation modifies the description

  • Custom User Avatar

    Approved

  • Custom User Avatar

    Haskell translation

    • Description updated to add Haskell-specific block describing the change in the input/output type differences.
  • Custom User Avatar

    Haskell translation

    • Description has been updated with a language-specific block describing the input/output types.
  • Custom User Avatar

    Great practical kata, yet easy and simple.

  • Custom User Avatar

    Oh I see where we fucked up the random tests. No idea how mauros solution was timing out though, works fine for us if we fix the issue.

  • Custom User Avatar

    .

  • Custom User Avatar
    1. There is an F-word in the comments of the full test suite.
    2. Almost all random tests can be passed by simply returning None. Fork this to address it. (Using Voile's solution; mauro-1's solution somehow timed out every time I tried it.)
  • Custom User Avatar

    If anyone has any suggestions as to how to nicely generate tests for the second point then fire away.

  • Custom User Avatar

    The random tests generate keys/values as 3/4 letter uppercase strings, depending on what languages you speak some of these could be interpreted as offensive. That's all I got. I'm not changing it because, quite frankly, having a multiple thousand word list of every possible slur/whatever in the tests is infinitely more offensive than the computer choosing 4 letters at random.

    As for the other point I rewrote the entire test generation but didn't change it's behaviour (beyond what was probably intended, the original code was legitimately the worst we've seen in a long while).

  • Custom User Avatar

    What are you talking about?

  • Loading more items...