• Sign Up
    Time to claim your honor
  • Training
  • Practice
    Complete challenging Kata to earn honor and ranks. Re-train to hone technique
  • Freestyle Sparring
    Take turns remixing and refactoring others code through Kumite
  • Community
  • Leaderboards
    Achieve honor and move up the global leaderboards
  • Chat
    Join our Discord server and chat with your fellow code warriors
  • Discussions
    View our Github Discussions board to discuss general Codewars topics
  • About
  • Docs
    Learn about all of the different aspects of Codewars
  • Blog
    Read the latest news from Codewars and the community
  • Log In
  • Sign Up
depial Avatar
Name:Unknown
Clan:Unknown
Member Since:Aug 2020
Last Seen:May 2025
Profiles:
    Following:0
    Followers:19
    Allies:0
    View Profile Badges
    • Stats
    • Kata
    • Collections
    • Kumite
    • Social
    • Discourse
    • Conversations (328)
    • Replies
    • Authored
    • Needs Resolution
    • Custom User Avatar
      • Chrono79
      • commented on "Sort Arrays (Ignoring Case)" julia solution
      • 2 months ago

      I can't see who you're talking about, but normally that happens when some user is banned.

    • Custom User Avatar
      • depial
      • commented on "Sort Arrays (Ignoring Case)" julia solution
      • 2 months ago

      Why has this person's honor/etc. been erased?

    • Custom User Avatar
      • depial
      • commented on ""Regular Expression - Check if divisible by 0b111 (7)" Julia Translation"
      • 9 months ago

      Quite the optimist :D

    • Custom User Avatar
      • leofun01
      • commented on ""Regular Expression - Check if divisible by 0b111 (7)" Julia Translation"
      • 9 months ago

      That's ok, someone else will approve it.

    • Custom User Avatar
      • depial
      • commented on ""Regular Expression - Check if divisible by 0b111 (7)" Julia Translation"
      • 9 months ago

      Your changes look good, but since it's a fork of my translation, I can't approve it. However, if you made your own, separate translation, I would be able to.

    • Custom User Avatar
      • depial
      • commented on ""Symbolic differentiation of prefix expressions" Julia Translation"
      • 9 months ago

      Merge conflict due to:

      recent changes from related record must be merged first.

    • Custom User Avatar
      • depial
      • commented on ""Affordable Vacation" Julia Translation"
      • 11 months ago

      Unfortunately the Julia unit test is very unexpressive and only prints a message on a failure. However, I've changed how the test names are shown (now they are findmincost(money, days, cost) --> expected). The only other option I can think of would be to assign them to variables which look like the test names you suggest (e.g. Cheapest_day_rental = findmincost(money, days, cost) -> Cheapest_day_rental --> expected. Also, I've added the length of the cost array to the extra large random tests. Let me know what if you have any other thoughts. Cheers!

      Edit: While the changes I made show up here, they don't appear on the kata or in the run output. Not sure why

    • Custom User Avatar
      • OsipovKonstantin
      • commented on ""Affordable Vacation" Julia Translation"
      • 11 months ago

      Excellent!

      • Additionally, I would include the output of the number of elements in cost (length of cost) in the Extra Large Random Tests, ensuring all input data is shown in the error message
      • It's better to name individual random tests differently. Instead of using 'occurred --> expected', it's preferable to use 'Small random test 1', 'Medium random test 4', and so on.
      • In the basic tests, I would suggest adopting a similar approach to other languages. For instance, name the test 'Single day rental' or 'Cheapest day rental', and include the values of the variables money, days, and cost in the error message
      • The value of 'days' is fixed across all 10 tests. It would be better to make it different for each individual test
    • Custom User Avatar
      • pitipatw
      • commented on "Friend or Foe?" julia solution
      • 11 months ago

      Thank you for the reply! This really clears things out.

    • Custom User Avatar
      • depial
      • commented on "Friend or Foe?" julia solution
      • 11 months ago

      This is just another way to define a function, so there should be no perfomance difference. It's mentioned in the docs as "assignment form". It's often preferable when it can be used while remaining readable like in this example. I like to do this for fun, however, if you see some of my more contrived "assignment form" solutions on codewars, in practice, they often could be better as full function definitions to improve readability, by expanding out, and/or performance, by using more efficient algorithms/memory management/etc which the compactification didn't allow for.

    • Custom User Avatar
      • pitipatw
      • commented on "Friend or Foe?" julia solution
      • 11 months ago

      Performance-wise, would this be better or worse than defining a function and why?

    • Custom User Avatar
      • depial
      • commented on ""Find the vowels" Julia Translation"
      • 12 months ago

      For any other future reviewers:

      I've fixed the issues raised below, with the exception of adding type annotations to the function because there was no valid reason given by the previous reviewer. From what I can find, type declarations are not added arbitrarily to functions in Julia:

      • Not necessary
      • Not idiomatic
      • Optional at best

      If I've missed something, either about this being a codewars platform issue or if it is indeed idomatic to include type declarations, please let me know and I'll change that part of the code. Otherwise I'll leave it as idomatic as I know how to.

    • Custom User Avatar
      • depial
      • commented on ""Find the vowels" Julia Translation"
      • 12 months ago

      I've gone ahead and made it "Failed for: $(repr(word))", which I presume you meant. This now prints with quotes around the input.

      Could you clarify why you would like to annotate the function types? From everything I've seen, it is not idomatic in Julia to do that for every function. Usually it's only done when there is multiple dispatch or performance concerns, and I don't see either of those in this kata.

    • Custom User Avatar
      • depial
      • commented on ""Find the vowels" Julia Translation"
      • 12 months ago

      Why include types in a 7 kyu?

      In many languages with optional type declarations, adding declarations is the principal way to make code run faster. This is not the case in Julia. In Julia, the compiler generally knows the types of all function arguments, local variables, and expressions.

      Fixed the facts \ context issue.

    • Custom User Avatar
      • ejini战神
      • commented on ""Find the vowels" Julia Translation"
      • 12 months ago
      • Missing types in initial solution setup and reference solution

      • 2nd facts should be context in sample tests

      • Assertion messages should be Failed for: repr($word)

    • Loading more items...
    • © 2025 Codewars
    • About
    • API
    • Blog
    • Privacy
    • Terms
    • Code of Conduct
    • Contact

    Confirm

    • Cancel
    • Confirm

    Collect: undefined

    Loading collection data...