Skip to content

[RFC]: add @stdlib/assert/is-palindrome #6391

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

Open
3 tasks done
TamimEhsan opened this issue Mar 26, 2025 · 2 comments
Open
3 tasks done

[RFC]: add @stdlib/assert/is-palindrome #6391

TamimEhsan opened this issue Mar 26, 2025 · 2 comments
Labels
Feature Issue or pull request for adding a new feature. Needs Discussion Needs further discussion. RFC Request for comments. Feature requests and proposed changes.

Comments

@TamimEhsan
Copy link

Description

This RFC proposes to add a new assert util to check if a string is palindrome or not.

Related Issues

No.

Questions

No.

Other

Reference: Palindrome | Wikipedia

Checklist

  • I have read and understood the Code of Conduct.
  • Searched for existing issues and pull requests.
  • The issue name begins with RFC:.
@stdlib-bot
Copy link
Contributor

👋 Hi there! 👋

And thank you for opening your first issue! We will get back to you shortly. 🏃 💨

@kgryte kgryte added the RFC Request for comments. Feature requests and proposed changes. label Mar 29, 2025
@kgryte
Copy link
Member

kgryte commented Mar 29, 2025

In your RFC, I suggest also including (a) the proposed package name, (b) example usage, and (c) any potential gotchas. E.g., how will you handle surrogate pairs and grapheme clusters?

@kgryte kgryte added Feature Issue or pull request for adding a new feature. Needs Discussion Needs further discussion. labels Mar 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Issue or pull request for adding a new feature. Needs Discussion Needs further discussion. RFC Request for comments. Feature requests and proposed changes.
Projects
None yet
Development

No branches or pull requests

3 participants