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.

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

Handle closure types #77

Closed
ilyapuchka opened this issue Dec 25, 2016 · 4 comments
Closed

Handle closure types #77

ilyapuchka opened this issue Dec 25, 2016 · 4 comments
Assignees

Comments

@ilyapuchka
Copy link
Collaborator

As mentioned in #72 we may add support for closures, to detect variables/method parameters types being closures, detect number and types of their arguments (may correlate with #48). Will require to strip unneeded spaces as SourceKit does not do that for type names

@krzysztofzablocki
Copy link
Owner

@ilyapuchka do we want to add just basic closure as parameter handling to #72 before merging? I'm thinking that without this it might prevent implementing some features with method reflection?

@ilyapuchka
Copy link
Collaborator Author

As for now I'm imagining using methods reflection for generating methods overrides and being able to construct a method calls, but all of that will require at most passing parameters to original method using their names, as maximum knowing their type names, but no more info about arguments is required.
For 1.0 I would maybe even limit closures support by just detecting closures and stripping unneeded white spaces in their signature.

@krzysztofzablocki
Copy link
Owner

@ilyapuchka yeah that was my thinking, so do you want to add that to your pr before we merge it?

@ilyapuchka
Copy link
Collaborator Author

I was thinking to do that separately, maybe along with tuples support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants