Replies: 1 comment
-
Hi,
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would like your opinion on two topics, before I present you a pull request.
Returning Tasks when possible instead of awaiting them
There are still places in your library where a function returns an awaited result value while it could just return the Task, as the return statement is the last line in that function. Meaning this
can be changed to this
thus it will be the above code that will await the task. While now the task is awaited twice.
What is your opinion on this observation?
usage of .configureawait(false)
At some point in time, a lot of .configureawait(false) statements where added to your library. But I have noticed that this isn't used throughout your code. Is this deliberate? Is there a rationale behind the current use? Sometimes Functions use .configureawait(false) while other, similar functions do not.
Beta Was this translation helpful? Give feedback.
All reactions