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.

Sign up for GitHub

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

Jump to bottom

AsyncRx.NET's Do operator overloads more prone to ambiguity than normal Rx.NET' #2170

Open
idg10 opened this issue Oct 7, 2024 · 0 comments
Open

AsyncRx.NET's Do operator overloads more prone to ambiguity than normal Rx.NET' #2170

idg10 opened this issue Oct 7, 2024 · 0 comments
Labels
[area] AsyncRx

Comments

@idg10
Copy link
Collaborator

idg10 commented Oct 7, 2024 •
edited
Loading

There are overloads of AsyncEnumerable.Do that accept an Action<Exception>. The problem with this is that is can lead to ambiguity with the one that accepts an Action<T>.

This has caused problems as we start to try to make the existing test suite for Rx.NET work on AsyncRx.NET.

Normal Rx.NET seems to avoid this by offering a more selective set of overloads. We should probably follow suit in AsyncRx.NET.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[area] AsyncRx
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@idg10