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

add length() and is_empty() to Buffer #1044

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rami3l
Copy link
Contributor

@rami3l rami3l commented Sep 26, 2024

As required in the Markdown parser implementation.

Copy link
Contributor

coderabbitai bot commented Sep 26, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

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.


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 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.

@coveralls
Copy link
Collaborator

coveralls commented Sep 26, 2024

Pull Request Test Coverage Report for Build 3588

Details

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.007%) to 82.326%

Totals Coverage Status
Change from base Build 3580: 0.007%
Covered Lines: 4197
Relevant Lines: 5098

💛 - Coveralls

@@ -72,6 +72,16 @@ fn grow_if_necessary(self : Buffer, required : Int) -> Unit {
}
}

/// Return the given buffer's length in bytes.
Copy link
Contributor

Choose a reason for hiding this comment

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

this is encoding agnostics? How is it useful

Copy link
Contributor Author

@rami3l rami3l Sep 29, 2024

Choose a reason for hiding this comment

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

@bobzhang This API mirrors OCaml's Buffer.length which counts in bytes (i.e. chars in OCaml), so it is indeed encoding agnostic. Currently it's feasible via b.to_bytes().length() (example), but .to_bytes() introduces an extra copy.

Although in Cmarkit this API is only used to check whether the buffer is empty (namely length b <> 0), other use cases do exist, notably getting a copy of the underlying Bytes towards its end via Buffer.sub (e.g. sub b 42 (length b - 1 - 42)).

Thus, I think it would still be beneficial to expose the buffer length. Of course, I'd be happy to withdraw the .length() API if you consider this to be unnecessary.

Copy link
Contributor

Choose a reason for hiding this comment

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

we are moving buffer outside builtin to provide a dedicated buffer package mimicking ocaml's behavior cc @hackwaly

@hackwaly
Copy link
Contributor

related #1084

@bobzhang
Copy link
Contributor

@rami3l can you cherry pick these APIs into the new buffer package

Copy link

peter-jerry-ye-code-review bot commented Oct 12, 2024

From the provided git diff output, I observe the following potential issues or suggestions for improvement in the MoonBit code:

  1. Potential Bug in length Function:

    • The length function returns the length of the buffer in bytes (self.len). However, the comment states that it returns the buffer's length in bytes, which is redundant. It would be helpful to clarify if this is indeed the intended behavior or if there is a misunderstanding in the comment.
    /// Return the given buffer's length in bytes.
    pub fn length(self : Buffer) -> Int {
      self.len
    }
    
  2. Potential Redundancy in is_empty Function:

    • The is_empty function checks if the buffer length is zero (self.len == 0). The comment suggests that it returns whether the buffer is empty, which aligns with the code. However, the comment could be more concise for clarity.
    /// Return whether the given buffer is empty.
    pub fn is_empty(self : Buffer) -> Bool {
      self.len == 0
    }
    
  3. Potential Typo in Test Comments:

    • In the test comments for the length method and is_empty method, the word "method" is repeated. This might be a small typo but can be corrected for better readability.
    test "length method" {
      let buf = @buffer.new(size_hint=100)
      inspect!(buf.length(), content="0")
      buf.write_string("Test")
      inspect!(buf.length(), content="8")
    }
    
    test "is_empty method" {
      let buf = @buffer.new(size_hint=100)
      inspect!(buf.is_empty(), content="true")
      buf.write_string("Test")
      inspect!(buf.is_empty(), content="false")
    }
    

These observations are based on the provided git diff output and the context provided in the MoonBit language reference.

@rami3l
Copy link
Contributor Author

rami3l commented Oct 12, 2024

@rami3l can you cherry pick these APIs into the new buffer package

@bobzhang Rebased.

@rami3l
Copy link
Contributor Author

rami3l commented Oct 16, 2024

May I ask what is blocking this PR from being merged? Many thanks in advance :)

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.

4 participants