Added C# solutions for Chapter 1 (Two Pointers)

[emseto]

• is_palindrome_valid
• largest_container
• largest_container_brute_force
• next_lexicographical_sequence
• pair_sum_sorted
• pair_sum_sorted_brute_force
• shift_zeros_to_the_end
• shift_zeros_to_the_end_naive
• triplet_sum
• triplet_sum_brute_force

This follows the naming conventions as described in C# identifier naming rules and conventions.

I'm open to modifying class names if there's something more appropriate. Added unit tests for Chapter 1: Two Pointers here.

[Destiny-02]

Hi @emseto, thanks for making the first PR to the C# solutions!

I noticed you used public partial class Solution. Are there any downsides to using public class Solution instead? We want to go with the more familiar option.

[emseto]

Hi @Destiny-02, thank you for taking a look at the PR! The reason why I used partial classes instead is related to testing and organizing the solutions. Partial classes allow a single class to be split across multiple files, which helps keep methods for individual solutions separate. However, I recognize that this isn't ideal. In an ideal scenario, each file would have a unique class name.

There are a couple of constraints in C# to note:

1. Class names and methods should follow Pascal case.
2. Class names and methods cannot be the same unless the method is a constructor.

Because I wasn't sure what to name each class, I settled on public partial class Solution instead of public class Solution to group the solution methods while avoiding naming conflicts.

There are a few ways of remedying this, including:

1. Assign unique namespaces for each solution (e.g. for IsValidPalindrome, we could have namespace TwoPointers.IsValidPalindrome with public class Solution).
2. Provide a unique class name for each solution (e.g. for IsValidPalindrome, we could have have IsValidPalindromeSolution class if we wanted to keep the method as IsValidPalindrome).

If each file is going to be self-contained, then I can go ahead and update public partial class Solution to public class Solution. Please let me know your thoughts, and I can make the necessary updates.

[Destiny-02]

Hi @Destiny-02, thank you for taking a look at the PR! The reason why I used partial classes instead is related to testing and organizing the solutions. Partial classes allow a single class to be split across multiple files, which helps keep methods for individual solutions separate. However, I recognize that this isn't ideal. In an ideal scenario, each file would have a unique class name.

There are a couple of constraints in C# to note:

1. Class names and methods should follow Pascal case.
2. Class names and methods cannot be the same unless the method is a constructor.

Because I wasn't sure what to name each class, I settled on public partial class Solution instead of public class Solution to group the solution methods while avoiding naming conflicts.

There are a few ways of remedying this, including:

1. Assign unique namespaces for each solution (e.g. for IsValidPalindrome, we could have namespace TwoPointers.IsValidPalindrome with public class Solution).
2. Provide a unique class name for each solution (e.g. for IsValidPalindrome, we could have have IsValidPalindromeSolution class if we wanted to keep the method as IsValidPalindrome).

If each file is going to be self-contained, then I can go ahead and update public partial class Solution to public class Solution. Please let me know your thoughts, and I can make the necessary updates.

Thanks for the explanation @emseto! In this case, we'd like to use public class Solution, even though it will cause an error when the folder is downloaded. Each file will be self-contained and you can think about it like the code will be pasted into an online judge IDE.

[emseto]

Hi @Destiny-02 , sounds good and thank you for the clarification! I've updated the PR.

[Destiny-02]

LGTM!