Open
Conversation
3 tasks
sowelipililimute
suggested changes
Mar 11, 2026
sowelipililimute
approved these changes
Mar 12, 2026
Tayrtahn
reviewed
Mar 14, 2026
This was referenced Mar 15, 2026
a17621e to
8b56561
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes EntityQuery usable in
foreachloops, as a replacement forEntityQueryEnumerator<T>andAllEntityQueryEnumerator<T>.Additionally, 2, 3, and 4 argument EntityQuery has been introduced.
you can finally
and expect it to not only work but also be optimal (I verified that the generated IL is expectedly efficient, and does not allocate.)
This additionally starts work on introducing a "proper" query engine, with DynamicEntityQuery, which allows you to mark entries in the query as optional (i.e. allowed to not be present, but looked up regardless) or excluded (must not be present).