LeetCode #2619 — EASY

Array Prototype Last

Build confidence with an intuition-first walkthrough focused on core interview patterns fundamentals.

The Problem

Problem Statement

Write code that enhances all arrays such that you can call the array.last() method on any array and it will return the last element. If there are no elements in the array, it should return -1.

You may assume the array is the output of JSON.parse.

Example 1:

Input: nums = [null, {}, 3]
Output: 3
Explanation: Calling nums.last() should return the last element: 3.

Example 2:

Input: nums = []
Output: -1
Explanation: Because there are no elements, return -1.

Constraints:

arr is a valid JSON array
0 <= arr.length <= 1000

Step 01

Brute Force Baseline

Problem summary: Write code that enhances all arrays such that you can call the array.last() method on any array and it will return the last element. If there are no elements in the array, it should return -1. You may assume the array is the output of JSON.parse.

Baseline thinking

Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.

Pattern signal: General problem-solving

Example 1

[null, {}, 3]

Example 2

[]

Core Insight

What unlocks the optimal approach

Inside the Array.prototype.last function body, you have access to the "this" keyword. "this" is equal to the contents of the array in this case.
You can access elements in the array via this[0], this[1], etc. You can also access properties and method like this.length, this.forEach, etc.

Interview move: turn each hint into an invariant you can check after every iteration/recursion step.

Step 03

Algorithm Walkthrough

Iteration Checklist

Define state (indices, window, stack, map, DP cell, or recursion frame).
Apply one transition step and update the invariant.
Record answer candidate when condition is met.
Continue until all input is consumed.

Use the first example testcase as your mental trace to verify each transition.

Step 04

Edge Cases

Minimum Input

Single element / shortest valid input

Validate boundary behavior before entering the main loop or recursion.

Duplicates & Repeats

Repeated values / repeated states

Decide whether duplicates should be merged, skipped, or counted explicitly.

Extreme Constraints

Upper-end input sizes

Re-check complexity target against constraints to avoid time-limit issues.

Invalid / Corner Shape

Empty collections, zeros, or disconnected structures

Handle special-case structure before the core algorithm path.

Step 05

Full Annotated Code

Source-backed implementations are provided below for direct study and interview prep.

// Accepted solution for LeetCode #2619: Array Prototype Last
// Auto-generated Java example from ts.
class Solution {
    public void exampleSolution() {
    }
}
// Reference (ts):
// // Accepted solution for LeetCode #2619: Array Prototype Last
// declare global {
//     interface Array<T> {
//         last(): T | -1;
//     }
// }
// 
// Array.prototype.last = function () {
//     return this.length ? this.at(-1) : -1;
// };
// 
// /**
//  * const arr = [1, 2, 3];
//  * arr.last(); // 3
//  */
// 
// export {};

// Accepted solution for LeetCode #2619: Array Prototype Last
// Auto-generated Go example from ts.
func exampleSolution() {
}
// Reference (ts):
// // Accepted solution for LeetCode #2619: Array Prototype Last
// declare global {
//     interface Array<T> {
//         last(): T | -1;
//     }
// }
// 
// Array.prototype.last = function () {
//     return this.length ? this.at(-1) : -1;
// };
// 
// /**
//  * const arr = [1, 2, 3];
//  * arr.last(); // 3
//  */
// 
// export {};

# Accepted solution for LeetCode #2619: Array Prototype Last
# Auto-generated Python example from ts.
def example_solution() -> None:
    return
# Reference (ts):
# // Accepted solution for LeetCode #2619: Array Prototype Last
# declare global {
#     interface Array<T> {
#         last(): T | -1;
#     }
# }
# 
# Array.prototype.last = function () {
#     return this.length ? this.at(-1) : -1;
# };
# 
# /**
#  * const arr = [1, 2, 3];
#  * arr.last(); // 3
#  */
# 
# export {};

// Accepted solution for LeetCode #2619: Array Prototype Last
// Rust example auto-generated from ts reference.
// Replace the signature and local types with the exact LeetCode harness for this problem.
impl Solution {
    pub fn rust_example() {
        // Port the logic from the reference block below.
    }
}

// Reference (ts):
// // Accepted solution for LeetCode #2619: Array Prototype Last
// declare global {
//     interface Array<T> {
//         last(): T | -1;
//     }
// }
// 
// Array.prototype.last = function () {
//     return this.length ? this.at(-1) : -1;
// };
// 
// /**
//  * const arr = [1, 2, 3];
//  * arr.last(); // 3
//  */
// 
// export {};

// Accepted solution for LeetCode #2619: Array Prototype Last
declare global {
    interface Array<T> {
        last(): T | -1;
    }
}

Array.prototype.last = function () {
    return this.length ? this.at(-1) : -1;
};

/**
 * const arr = [1, 2, 3];
 * arr.last(); // 3
 */

export {};

Step 06

Interactive Study Demo

Use this to step through a reusable interview workflow for this problem.

Custom checkpoints (one per line)

Press Step or Run All to begin.

Step 07

Complexity Analysis

Time

O(n)

Space

O(1)

Approach Breakdown

BRUTE FORCE

O(n²) time

O(1) space

Two nested loops check every pair or subarray. The outer loop fixes a starting point, the inner loop extends or searches. For n elements this gives up to n²/2 operations. No extra space, but the quadratic time is prohibitive for large inputs.

OPTIMIZED

O(n) time

O(1) space

Most array problems have an O(n²) brute force (nested loops) and an O(n) optimal (single pass with clever state tracking). The key is identifying what information to maintain as you scan: a running max, a prefix sum, a hash map of seen values, or two pointers.

Shortcut: If you are using nested loops on an array, there is almost always an O(n) solution. Look for the right auxiliary state.

Coach Notes

Common Mistakes

Review these before coding to avoid predictable interview regressions.

Off-by-one on range boundaries

Wrong move: Loop endpoints miss first/last candidate.

Usually fails on: Fails on minimal arrays and exact-boundary answers.

Fix: Re-derive loops from inclusive/exclusive ranges before coding.