Skip to content

Fix some small list -> Iterable/Sequence typing issues #1590

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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

CarliJoy
Copy link

"List" are invariant (see https://mypy.readthedocs.io/en/stable/common_issues.html#variance), so we really should try to avoid them, especially as input parameter for our functions.

Stubled upon the following places where it clashed with my type checking.

Maybe there are more but start small ;-)

Given be the usage of words, it does not need to be List nor Sequence only an Iterable
StyleAndTextTuples = List[OneStyleAndTextTuple]

# For typing stuff, we prefer an Iterable as it is more flexible
StyleAndTextTuplesType = Iterable[OneStyleAndTextTuple]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure that Iterable is desirable, because it means it's not indexable and possibly, can only be consumed once.
Without reading again through all of the prompt_toolkit codebase, I think Sequence is at least what we need.

@@ -31,7 +31,7 @@ class WordCompleter(Completer):

def __init__(
self,
words: Union[List[str], Callable[[], List[str]]],
words: Union[Iterable[str], Callable[[], Iterable[str]]],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make this at least a Sequence.

Otherwise, users are going to pass in a generator of strings, and wonder why the second time, they're not getting any completions.

Is there a reason it should be Iterable here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review @jonathanslenders

Nope. I was just going to use the lowest possible. You are right a Sequence would be more fitting.

I stopped working on this PR as some other troubles occured (see failing tests)
Once I found time to resolve them, I will undraft the PR and ping you.

@CarliJoy CarliJoy marked this pull request as draft March 15, 2022 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants