-
Notifications
You must be signed in to change notification settings - Fork 5k
[metadata] Don't access MonoTableInfo:rows, use table_info_get_rows() #49738
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.
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
Conversation
Tagging subscribers to this area: @CoffeeFlux Issue DetailsRename the field to rows_. Also updated some bounds checks to use mono_metadata_table_bounds_check (which Added FIXME: metadata-update in cases where the table row size is assumed to be Contributes to #44806
|
Think you need to rebase this. |
5b43d2d
to
ed58d86
Compare
Rename the field to rows_. Also updated some bounds checks to use mono_metadata_table_bounds_check (which is metadata-update aware) where the subsequent lookups go through the metadata decode functions and should just work with metadata-update. Added FIXME: metadata-update in cases where the table row size is assumed to be fixed or is used as a sentinel value, or where the decoding may depend on sorting properties that metadata updates probably won't uphold.
ed58d86
to
f22794c
Compare
@vargaz could you please review the change? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Hi @lambdageek, I think this patch introduced a regression here https://github.com/dotnet/runtime/pull/49738/files#diff-9bd9d0e46241d07dc62110246c89c9f056333eff4b0b089551780a625c871d0dL1982: This used to set
|
Thanks @uweigand! |
Rename the field to rows_.
Also updated some bounds checks to use mono_metadata_table_bounds_check (which
is metadata-update aware) where the subsequent lookups go through the metadata
decode functions and should just work with metadata-update.
Added FIXME: metadata-update in cases where the table row size is assumed to be
fixed or is used as a sentinel value, or where the decoding may depend on
sorting properties that metadata updates probably won't uphold.
Contributes to #44806