[Feature Request]:

[NAVJOT-786]

Is there an existing issue for this?

• I have searched the existing issues

Feature Description

I would like to add a problem statement and solution for the coding problem "2704. To Be Or Not To Be" to the repository. This will involve including the problem description, constraints, example test cases, and a well-documented solution in the appropriate section of the repository.

Use Case

The documentation should be updated to include the "2704. To Be Or Not To Be" problem under a new section dedicated to string manipulation challenges. This section will provide a detailed explanation of the problem, a step-by-step solution, and corresponding code examples.

Benefits

The update should include:

A clear and concise problem description for "2704. To Be Or Not To Be."
Constraints and edge cases to consider when solving the problem.
Example test cases to illustrate the problem.
A well-commented solution in the programming language used in the repository.
An explanation of the approach and logic behind the solution.

Add ScreenShots

No response

Priority

High

Record

• I have read the Contributing Guidelines
• I'm a GSSOC'24 contributor
• I have starred the repository

[github-actions]

Hi @NAVJOT-786! Thanks for opening this issue. We appreciate your contribution to this open-source project. Your input is valuable and we aim to respond or assign your issue as soon as possible. Thanks again!

[github-actions]

Hello @NAVJOT-786! Your issue #4258 has been closed. Thank you for your contribution!