-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
Callsite fix for async methods #1138
Conversation
Current coverage is
|
@@ -31,6 +31,9 @@ | |||
// THE POSSIBILITY OF SUCH DAMAGE. | |||
// | |||
|
|||
using System.IO; | |||
using System.Threading.Tasks; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Must these using
statements not go inside the namespace
block?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would be more consistent yes. Resharper did this for me, but will fix it (cannot configure this in Resharper AFAIK)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed Visual Studio's "Quick Actions" adds the using
inside the namespace
(if there are no using
s outside of it). Interesting.
I don't find anything wrong with the logic of the code, but I made a few suggestions related to the code itself. |
@bhaeussermann Thanks for your suggestions. I applied them and renamed and documented a bit. Please check in short and if you think it's OK, merge it :) |
if (next != null) | ||
{ | ||
var declaringType = next.StackFrame.GetMethod().DeclaringType; | ||
if (declaringType != null && declaringType == typeof(System.Runtime.CompilerServices.AsyncTaskMethodBuilder)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This null
test is redundant now.
it seems we have a deadlock in the master :( @bhaeussermann any idea if this is fixed in another PR? |
Not that I know of. |
Well I was hoping #1126 would fix it. |
Rebuild all. I don't think this one introduces a new deadlock. So if it al builds, it can be merged |
Callsite fix for async methods
fixes #255