-
Notifications
You must be signed in to change notification settings - Fork 815
Tests the scenario when calling protected static base member from static do
#17484
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
Tests the scenario when calling protected static base member from static do
#17484
Conversation
static do
static do
|
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.
Thanks for looking into it and testing!
@KevinRansom @vzarytovskii do we have an ambition to make it work with realsig- as well, or should we just close the issue for good?
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.
Thank you for highlighting the super-old issue and adding these tests. I will see what can be done to make realsig- succeed in this case. We don't really want there to be a behaviour difference between on and off.
tests/FSharp.Compiler.ComponentTests/EmittedIL/RealInternalSignature/RealInternalSignature.fs
Show resolved
Hide resolved
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Description
It seems that the linked issue not longer happens when
--realsig+
is enabled. So this PR adds tests to demonstrate thisChecklist