Conversation
… metadata tables
|
r? @Zalathar , for example, I've seen you refactoring the metadata infra recently |
|
|
|
Could you explain more about From the PR description and commit message, I wasn't able to get a good sense of why this change is desirable, or whether it's even correct. |
It was the only table that has |
|
So if I understand correctly:
If so, could you please update the commit message and PR description to clearly explain the reasoning to future maintainers, and remove the misleading stuff about usize? |
…ly when `ProcMacroData` is `Some`
cc26ffb to
020ffe1
Compare
Updated commit message and PR description. |
|
Thanks. I will also say that normally I would be against adding the macros, but I guess it makes sense if they’re specifically for enabling a tricky change to how def-indexes work. I do hope that we can remove the macros after those changes, though. |
…ome` and `record_defaulted` -> `record_value`
Two refactorings that were extracted from #162809:
proc_macro_quoted_spanstable intoProcMacroDataas it is filled only whenProcMacroDataisSome(meaning crate type isproc-macro), so it is reasonable to place it here, moreover all tables left inLazyTableshaveDefIndexas key, this simplifies refactorings and modifications that are connected withDefIndexes.r? @petrochenkov