-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[WIP] Introduce SingletonCache
for use with ZST query keys
#86119
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Otherwise, we can get an ambiguity error (with multiple comma-separated modifiers) because the parents can either be parsed as the 'arg', or part of the undifferentiated 'other arguments'
This reverts commit a03cf1b.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 75ee1ed with merge 1ed439959dd9b1f13c824476eaa0477cfddc3b63... |
☀️ Try build successful - checks-actions |
Queued 1ed439959dd9b1f13c824476eaa0477cfddc3b63 with parent e4a6032, future comparison URL. |
Finished benchmarking try commit (1ed439959dd9b1f13c824476eaa0477cfddc3b63): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Could it be used automatically for ZST query keys in the proc macro? |
Triage here, converting to a Draft PR to remove it from the triage queue. |
We already map |
Ping from triage: |
closing as inactive |
r? @ghost