linksplatform / linksplatform/Ranges

Can we simplify this?

Open
#45 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

It looks verdy difficult
https://github.com/linksplatform/Ranges/blob/d7b5ac881f7e8921520f5264ce04a1d97dfd31c3/cpp/Platform.Ranges/EnsureExtensions.h#L33-L43
Why do we create lambdas, recursively descend into other functions, sums a bunch of lines to check that an element is in the range? And why do we throw an exception if the element is not in the range, when we can return a boolean value? Can we simplify this?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading cpp/Platform.Ranges/EnsureExtensions.h at lines 33-43 and tracing the functions and lambdas used by the range check. Compare the current exception-based behavior with the proposed boolean result, then clarify the intended API and callers before defining what a successful simplification should preserve.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.