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

[WIP] Add no_unliteral flag to overloads #6043

Closed
wants to merge 1 commit into from

Conversation

ehsantn
Copy link
Collaborator

@ehsantn ehsantn commented Jul 28, 2020

This flag avoids calling overloads again without literal types if the first call with literals was unsuccessful.
Closes #5411.

I think having the opposite option of just calling without literals is also helpful to avoid overspecialization. So this flag can be renamed/expanded to support both.

This flag avoids calling overloads again without
literal types if the first call with literals was unsuccessful.
@ehsantn
Copy link
Collaborator Author

ehsantn commented Jul 28, 2020

@stuartarchibald This is the no_unliteral flag I mentioned last week. We have been using this significantly for a while now, but this may need to be expanded to support non-literal only case as well. Feel free to take code from this branch or just modify it.

@github-actions
Copy link

This pull request is marked as stale as it has had no activity in the past 3 months. Please respond to this comment if you're still interested in working on this. Many thanks!

@github-actions github-actions bot added the stale Marker label for stale issues. label Mar 31, 2023
@github-actions github-actions bot added the abandoned - stale PRs automatically closed due to stale status label Apr 8, 2023
@github-actions github-actions bot closed this Apr 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 - In Progress abandoned - stale PRs automatically closed due to stale status stale Marker label for stale issues.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid calling typers/overloads without literal types
3 participants