Skip to content

Latest commit

 

History

History
 
 

5_pad_array

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

Week 4 Home

U2.W4: Create a Method to Pad an Array

Learning Competencies

  • Use tests to guide development
  • Break down problems into implementable pseudocode
  • Differentiate between and produce destructive and non-destructive methods
  • Find and use built-in Ruby methods to solve challenges

Summary:

Implement Array#pad and Array#pad!. Each method accepts a minimum size (non-negative integer) and an optional pad value as arguments.

If the array's length is less than the minimum size, Array#pad should return a new array padded with the pad value up to the minimum size.

For example,

[1,2,3].pad(5)

should return

[1,2,3,nil,nil]

And

[1,2,3].pad(5, 'apple')

should return

[1,2,3,'apple', 'apple']

If the minimum size is less than or equal to the length of the array, it should just return the array.

That is, [1,2,3].pad(3) should return [1,2,3].

my_array.pad(0) should always return an array equal to my_array. Array#pad should always return a new object, i.e., it should be non-destructive.

Array#pad! behaves identically to Array#pad except that it modifies the underlying array.

##Release 0: Run the tests In your terminal, navigate to this directory and run the appropriate spec file. Each test should fail. Read the output in your terminal to see what is making the tests fail.

Release 1: Pseudocode

commit your changes

Release 2: Initial Solution

commit your changes

commit your changes

Release 4: Reflect

Include your reflection in the appropriate section in your my_solution file. NOTE: Reflections are mandatory! Commit your changes!

Release 5: Sync your repo with GitHub

When you feel confident with your solution, sync your changes through the GitHub desktop app with your repo on GitHub. If you have done this successfully, you should be able to see your new code on your repo on github.com.

Release 6: Review