Problem solution · Java

Task Scheduler

Task Scheduler: a Java solution using direct simulation. Learn the idea, check the complexity, and read the full code, with credit to walkccc LeetCode Solutions.

Technique
Direct simulation
Source
walkccc LeetCode Solutions
Length
21 lines
Start with the idea.

Try the problem first. If you get stuck, read the approach below, then write your own solution. The full code is at the bottom.

Approach

Direct simulation

For Task Scheduler, the implementation follows the problem’s operations directly while maintaining only the state needed for the next decision.

  1. Translate each rule into one explicit state update.
  2. Maintain the invariant after every processed item.
  3. Return the accumulated state once all relevant input has been handled.

Code notes

  • 21 lines of Java from the credited upstream file 621.java.
  • The implementation visibly relies on sequence storage.
  • 1 loop block detected.

Complexity

Count the number and nesting of passes over the input, then include the maintained containers in the memory estimate.

Check the problem constraints before deciding whether this complexity will pass.

Source

Code and credit

This code comes from walkccc LeetCode Solutions by P.-Y. Chen (walkccc) and is used under the MIT licence.

Full codeTask Scheduler · JavaJava
Use this to learn the idea, then write your own version.
class Solution {  public int leastInterval(char[] tasks, int n) {    int[] count = new int[26];     for (final char task : tasks)      ++count[task - 'A'];     final int maxFreq = Arrays.stream(count).max().getAsInt();    // Put the most frequent task in the slot first.    final int maxFreqTaskOccupy = (maxFreq - 1) * (n + 1);    // Get the number of tasks with the same frequency as `maxFreq`, we'll    // append them after `maxFreqTaskOccupy`.    final int nMaxFreq = (int) Arrays.stream(count).filter(c -> c == maxFreq).count();    // max(    //   the most frequent task is frequent enough to force some idle slots,    //   the most frequent task is not frequent enough to force idle slots    // )    return Math.max(maxFreqTaskOccupy + nMaxFreq, tasks.length);  }} 

Did this explanation save you time? I'm a Grade 11 student building this free library to make difficult algorithms easier to understand.

Buy me a coffee ↗