You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The theme of version 9 is to reduce the allocation as much as possible. We'll squeeze every unnecessary allocated byte.
In this context, Take and Skip properties are defined as nullable int values, where the null value means "not set". Considering that int? has a size of 8 bytes compared to 4 bytes for int (on x64), we'll update these properties to non-nullable int, and the default value will be defined as -1.
Breaking change:
The common use of this library will remain unchanged. But, folks who have custom evaluators, extensions, or have custom logic that depends on the specification state directly will be affected by this change.
The text was updated successfully, but these errors were encountered:
The theme of version 9 is to reduce the allocation as much as possible. We'll squeeze every unnecessary allocated byte.
In this context,
Take
andSkip
properties are defined as nullable int values, where the null value means "not set". Considering thatint?
has a size of 8 bytes compared to 4 bytes forint
(on x64), we'll update these properties to non-nullable int, and the default value will be defined as -1.Breaking change:
The common use of this library will remain unchanged. But, folks who have custom evaluators, extensions, or have custom logic that depends on the specification state directly will be affected by this change.
The text was updated successfully, but these errors were encountered: