Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature update - Add FDeque: Immutable Functional Double-Ended Queue and JUnit Tests #62

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

JesperSandklef
Copy link

@JesperSandklef JesperSandklef commented Feb 13, 2025

Summary by CodeRabbit

  • New Features
    • Introduced an immutable double-ended queue that enables efficient management of ordered collections. Users can now seamlessly add or remove items from both ends, ensuring improved consistency and reliable behavior.

@JesperSandklef JesperSandklef linked an issue Feb 13, 2025 that may be closed by this pull request
Copy link

coderabbitai bot commented Feb 13, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request introduces a new immutable, functional double-ended queue implementation through the FDeque<T> class. It supports operations for adding and removing elements from both ends, as well as peeking at the front and back elements and checking for emptiness. A static factory method is provided for instance creation. In addition, a comprehensive JUnit 5 test suite has been added to validate these operations.

Changes

File Summary
src/.../FDeque.java Added public final class FDeque<T> with methods: create(), enqueFront(), enqueBack(), dequeFront(), dequeBack(), peekFront(), peekBack(), and isEmpty().
src/.../FDequeTest.java Added JUnit 5 test class FDequeTest to validate the functionality of the FDeque methods including enqueue, dequeue, peek, and state checks.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant FDeque

    Client->>FDeque: create()
    FDeque-->>Client: new FDeque instance

    Client->>FDeque: enqueFront(item)
    FDeque-->>Client: new instance (updated front)

    Client->>FDeque: enqueBack(item)
    FDeque-->>Client: new instance (updated back)

    Client->>FDeque: peekFront()/peekBack()
    FDeque-->>Client: element value

    Client->>FDeque: dequeFront()/dequeBack()
    FDeque-->>Client: new instance (immutable update)
Loading

Poem

I'm a rabbit with hops so light,
Celebrating code that feels just right.
FDeque dances, immutable and true,
Enqueue and dequeue—each update new.
Hop along with tests that ensure delight!
🐰💻 Happy coding in pure functional light!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@JesperSandklef JesperSandklef marked this pull request as draft February 13, 2025 19:33
@coderabbitai coderabbitai bot changed the title Feature update - @coderabbitai Feature update - Add FDeque: Immutable Functional Double-Ended Queue and JUnit Tests Feb 13, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (7)
src/main/java/FDeque.java (5)

1-1: Remove unused import.

The ArrayList import is not used in the implementation.

-import java.util.ArrayList;

6-10: Add class-level documentation.

Consider adding class-level JavaDoc to describe the purpose and behavior of this immutable double-ended queue implementation.

+/**
+ * An immutable double-ended queue implementation that maintains elements in two internal lists.
+ * All operations return new instances, preserving immutability.
+ *
+ * @param <T> the type of elements held in this deque
+ */
 public final class FDeque<T> {

12-19: Add parameter validation in constructor.

While the constructor is private, it's still good practice to validate parameters to catch potential issues early.

 private FDeque(List<T> front, List<T> back) {
+    if (front == null || back == null) {
+        throw new IllegalArgumentException("Lists cannot be null");
+    }
     this.front = Collections.unmodifiableList(front);
     this.back = Collections.unmodifiableList(back);
 }

47-60: Fix inconsistent indentation in dequeue methods.

The indentation in both dequeue methods is inconsistent, making the code harder to read.

 public FDeque<T> dequeFront() {
     if (front.isEmpty() && back.isEmpty()) {
-            return create(); }
-         else if (front.isEmpty()) {
+        return create();
+    } else if (front.isEmpty()) {
         List<T> newBack = new LinkedList<>(back);
         newBack.removeFirst();
         return new FDeque<>(Collections.emptyList(), newBack);
     }
-         else {
+    } else {
         List<T> newFront = new LinkedList<>(front);
         newFront.removeFirst();
         return new FDeque<>(newFront, back);
     }
 }

 public FDeque<T> dequeBack() {
     if (back.isEmpty() && front.isEmpty()) {
-            return create();
-        } else if (back.isEmpty()) {
-            List<T> newFront = new LinkedList<>(front);
-            newFront.removeLast();
-            return new FDeque<>(Collections.emptyList(), newFront);
-        }
-        else {
+        return create();
+    } else if (back.isEmpty()) {
+        List<T> newFront = new LinkedList<>(front);
+        newFront.removeLast();
+        return new FDeque<>(Collections.emptyList(), newFront);
+    } else {
         List<T> newBack = new LinkedList<>(back);
         newBack.removeLast();
         return new FDeque<>(front, newBack);
     }
 }

Also applies to: 66-79


85-105: Consider using Optional for peek operations.

Instead of returning null for empty deques, consider using Optional to make the absence of a value more explicit.

-public T peekFront() {
+public Optional<T> peekFront() {
     if (!front.isEmpty()) {
-        return front.getFirst();
+        return Optional.of(front.getFirst());
     } else if (!back.isEmpty()) {
-        return back.getFirst();
+        return Optional.of(back.getFirst());
     }
-    return null;
+    return Optional.empty();
 }

-public T peekBack() {
+public Optional<T> peekBack() {
     if (!back.isEmpty()) {
-        return back.getLast();
+        return Optional.of(back.getLast());
     } else if (!front.isEmpty()) {
-        return front.getLast();
+        return Optional.of(front.getLast());
     }
-    return null;
+    return Optional.empty();
 }
src/test/java/FDequeTest.java (2)

5-89: Enhance test coverage with additional scenarios.

While the current tests are good, consider adding:

  1. Tests for null element handling
  2. Tests with different types (Integer, custom objects)
  3. Property-based testing for invariants

Example additional tests:

@Test
void testNullElement() {
    FDeque<String> deque = FDeque.create();
    assertThatThrownBy(() -> deque.enqueFront(null))
        .isInstanceOf(IllegalArgumentException.class);
    assertThatThrownBy(() -> deque.enqueBack(null))
        .isInstanceOf(IllegalArgumentException.class);
}

@Test
void testWithInteger() {
    FDeque<Integer> deque = FDeque.create();
    deque = deque.enqueFront(1).enqueBack(2);
    assertThat(deque.peekFront()).isEqualTo(1);
    assertThat(deque.peekBack()).isEqualTo(2);
}

73-78: Add assertions for peek after empty deque operations.

The test for empty deque operations should verify that peek operations still return null after dequeuing.

 @Test
 void testPeekOnEmptyList() {
     FDeque<String> deque = FDeque.create();
     assertThat(deque.peekFront()).isNull();
     assertThat(deque.peekBack()).isNull();
+    
+    // Verify peek still returns null after dequeue operations
+    deque = deque.dequeFront();
+    assertThat(deque.peekFront()).isNull();
+    assertThat(deque.peekBack()).isNull();
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b69c221 and 20aefb1.

📒 Files selected for processing (2)
  • src/main/java/FDeque.java (1 hunks)
  • src/test/java/FDequeTest.java (1 hunks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FDeque<T> (Functional Double-Ended Queue)
1 participant