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 next perf bottleneck is write_natural_field. I thought byte_sequence was used in memory images, but it turns out this is used instead:
typebyte_pattern_element = maybebytetypebyte_pattern = listbyte_pattern_element(* An element might have an address/offset, and it has some contents. *)typeelement = <| startpos : maybenatural
; length : maybenatural
; contents : byte_pattern
|>
Is there a reason why we use maybe byte instead of byte here?
Since element is used 140 times in the whole codebase, replacing it with something else is possible but definitely not trivial.
The text was updated successfully, but these errors were encountered:
The next perf bottleneck is
write_natural_field
. I thoughtbyte_sequence
was used in memory images, but it turns out this is used instead:Is there a reason why we use
maybe byte
instead ofbyte
here?Since
element
is used 140 times in the whole codebase, replacing it with something else is possible but definitely not trivial.The text was updated successfully, but these errors were encountered: