Skip to content

Conversation

@diaasami
Copy link
Contributor

Since data is accessed once and there's no need to keep it in memory

@diaasami diaasami force-pushed the generators branch 2 times, most recently from 5ae110f to a73266c Compare September 24, 2025 02:32
@diaasami diaasami changed the title Use generators instead of list comprehensions whenever possible Use generators instead of list comprehensions where it makes sense Sep 24, 2025
@diaasami diaasami changed the title Use generators instead of list comprehensions where it makes sense Use generators where it makes sense Sep 24, 2025
'updated': issue.fields.updated,
'description': issue.fields.description
}

Copy link
Member

Choose a reason for hiding this comment

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

(I know this is in draft, but) I think this change needs to be described in the commit message, or split into a separate commit.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

thanks for the feedback, what do you think now?

@diaasami diaasami marked this pull request as ready for review September 26, 2025 04:45
@diaasami diaasami force-pushed the generators branch 2 times, most recently from e88abbc to 5f1b9d7 Compare September 29, 2025 19:05
It's only used in cases where there is significant copying and big
objects, in other cases list comprehensions are fine
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