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.
  1. Prepare
  2. Ruby
  3. Control Structures
  4. Ruby Control Structures - Case (Bonus Question)
  5. Discussions

Ruby Control Structures - Case (Bonus Question)

Sort by

recency

|

84 Discussions

|

  • aliraza4130633
     + 0 comments

    Promotional products serve as powerful tools to strengthen brand visibility—just like Ruby control structures streamline decision-making in code. In the bonus case question, choosing the right case statement ensures clean, efficient logic, much like selecting the right branded item ensures lasting customer impact. Whether you're coding with precision or marketing with creativity, the right structure—be it in logic or promotion—leads to better outcomes and a more memorable user experience.

  • yashdeora98294
     + 0 comments

    Here is Ruby Control Structures - Case (Bonus Question) solution - https://programmingoneonone.com/hackerrank-ruby-control-structures-case-bonus-question-problem-solution.html

  • oli16
     + 0 comments

    why is: *case obj * and not: case obj.class

  • nickcameron
     + 1 comment

    If you're doing the same thing for each case, a case statement doesn't really make sense in my opinion.

    Here's a predicate that includes all of the conditions:

    [Hacker, Submission, TestCase, Contest].any? { |clazz| obj.is_a? clazz }

    You can use string interpolation (like in truesdell_trent1's comment here ) or just concatenation (with obj.class.name) to output the class names.

  • truesdell_trent1
     + 0 comments
    def identify_class(obj)
    # write your case control structure here
    case obj
    when Hacker
        puts "It's a #{obj.class}!"
    when Submission
        puts "It's a #{obj.class}!"
    when TestCase
        puts "It's a #{obj.class}!"
    when Contest
        puts "It's a #{obj.class}!"
    else
        puts "It's an unknown model"
    end 
end