• Sign Up
  • Kata
  • Kumite
  • Blog
  • Forum
  • Wiki
  • Leaders
  • Log In
  • Sign Up
Name:Unknown
Clan:Unknown
Member Since:Sep 2015
Last Seen:Aug 2018
Profiles:
Following:2
Followers:3
Allies:2
View Profile Badges
  • Stats
  • Kata
  • Collections
  • Kumite
  • Social
  • Discourse
  • Conversations (31)
  • Replies
  • Authored
  • Needs Resolution
    • FArekkusu
    • resolved an issue on "ThetaFormulation" kata

    Are you sure those are actually numbers?

    • HitriY
    • created an issue for "ThetaFormulation" kata

    This comment is hidden because it contains spoiler information about the solution

    • stellartux
    • created a suggestion for "ThetaFormulation" kata

    Julia translation

    • JohanWiltink
    • resolved a question on "ThetaFormulation" kata

    Added limited random tests ( expected value true will be generated exceedingly rarely. relying on fixed tests for that ).

    Smile, you missed an edge condition where you're returning NaN instead of null. You're not going to fix that anymore, I know. :P

    And approved.

    • JohanWiltink
    • created a question for "ThetaFormulation" kata

    This comment is hidden because it contains spoiler information about the solution

    • JohanWiltink
    • created an issue for "Degree or not Degree (Radian brooo)" kata

    If you're going to write a wrapper function for testing, make sure it can't be hijacked by solver ( defining it with const is one way to do that ).

    Native Math does not have enumerable properties. In keeping with this, and to teach good habits, defined methods should not be enumerable, and this should be tested for.

    toFixed does rounding differently from Math.round ( and weirdly in general ). This behaviour should be warned for and toFixed should ideally be discouraged and tested against.

    Rounding is not the appropriate solution for floating point representation inaccuracy. This has been dissed as an issue below, but again, it's teaching bad habits.

    • anter69
    • resolved an issue on "Grasshopper - Terminal game combat function" kata

    Not an issue

    • cliffstamp
    • resolved an issue on "Degree or not Degree (Radian brooo)" kata

    Updated description.

    • cliffstamp
    • resolved an issue on "Degree or not Degree (Radian brooo)" kata

    This is fixed, though not ideal.

    • Unnamed
    • created an issue for "Degree or not Degree (Radian brooo)" kata

    What kind of rounding is expected for values ending with 5?
    Existing solutions return different results for Math.toRadians(-60.87676573264997) and they all pass the tests.

    • Unnamed
    • created an issue for "Degree or not Degree (Radian brooo)" kata

    All tests are valid integers

    No really integers...

    • Unnamed
    • created an issue for "Degree or not Degree (Radian brooo)" kata

    Exact comparison isn't appropriate here due to possible floating point errors.

    • cliffstamp
    • resolved an issue on "Degree or not Degree (Radian brooo)" kata

    His point there is that saying that if it is a number and not a string, does it make sense to say things like don't pad or return the decimal.

    Description modified.

    • cliffstamp
    • resolved an issue on "Lowest product of 4 consecutive numbers" kata

    Duplicate.

    • Voile
    • resolved an issue on "Parsing Commandline Arguments" kata

    Since when is input validation required? ;-)

    Also descriptions has been updated

  • Loading more items...
  • © 2021 Codewars
  • About
  • API
  • Blog
  • Privacy
  • Terms
  • Contact
  • powered by

Confirm

  • Cancel
  • Confirm