We shouldn't use locking APIs when creating sets in bytecode #130312
Description
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