-
Notifications
You must be signed in to change notification settings - Fork 5
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
Extension methods are not included in completion proposals #30
Comments
I think what's happening is that the call to .allMembers on a Box node is not including extension methods because another Compiler instance is being created in between the time the completion list is generated and the next parse request starts. http://cobra-language.com/trac/cobra/browser/cobra/trunk/Source/Boxes.cobra#L119 I'm not sure yet but the first line of _allExtensionMembers is I need to stick some trace statements in there and see what's going on. |
Looks like |
Pretty much done and ready to merge into 'master' with the next release. Some issues which cannot be resolved with a non-thread safe compiler remain but it seems to work most of the time. |
Decided to remove this functionality after more testing revealed that race conditions frequently prevented these from working correctly. This will be addressed in the future with a new Cobra parser and type resolver. |
We want all appropriate extension methods to be displayed as dot completion proposals including things like
.toTechString
included for all objects and.md5HashInHex
included for Strings.The text was updated successfully, but these errors were encountered: