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.

Sign up for GitHub

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

Jump to bottom

We shouldn't use locking APIs when creating sets in bytecode #130312

Open
DinoV opened this issue Feb 19, 2025 · 0 comments
Open

We shouldn't use locking APIs when creating sets in bytecode #130312

DinoV opened this issue Feb 19, 2025 · 0 comments
Assignees
@DinoV
Labels
topic-free-threading type-feature A feature request or enhancement

Comments

@DinoV
Copy link
Contributor

DinoV commented Feb 19, 2025 •
edited by bedevere-app bot
Loading

Feature or enhancement

Proposal:

Currently we hit a locking API for populating sets during comprehensions and set literals. We should use a lock-free API as the object isn't exposed yet.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs
@DinoV DinoV added topic-free-threading type-feature A feature request or enhancement labels Feb 19, 2025
@DinoV DinoV self-assigned this Feb 19, 2025
@bedevere-app bedevere-app bot mentioned this issue Feb 19, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DinoV DinoV

Labels
topic-free-threading type-feature A feature request or enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DinoV