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
Original bug ID: 6869 Reporter: furuse Assigned to:@mshinwell Status: closed (set by @xavierleroy on 2016-12-07T10:49:22Z) Resolution: fixed Priority: normal Severity: major Version: 4.02.1 Fixed in version: 4.02.2+dev / +rc1 Category: standard library Monitored by:@gasche
Bug description
hashtbl.mli says about Hashtbl.hash_param:
Hashing performs a breadth-first, left-to-right traversal
of the structure [x], stopping after [meaningful] meaningful nodes
were encountered, or [total] nodes (meaningful or not) were
encountered.
The value of [total] is actually capped to HASH_QUEUE_SIZE=256 in byterun/hash.c therefore specifying larger than 256 is equivalent with 256. This should be noted in the comment.
The text was updated successfully, but these errors were encountered:
Original bug ID: 6869
Reporter: furuse
Assigned to: @mshinwell
Status: closed (set by @xavierleroy on 2016-12-07T10:49:22Z)
Resolution: fixed
Priority: normal
Severity: major
Version: 4.02.1
Fixed in version: 4.02.2+dev / +rc1
Category: standard library
Monitored by: @gasche
Bug description
hashtbl.mli says about Hashtbl.hash_param:
Hashing performs a breadth-first, left-to-right traversal
of the structure [x], stopping after [meaningful] meaningful nodes
were encountered, or [total] nodes (meaningful or not) were
encountered.
The value of [total] is actually capped to HASH_QUEUE_SIZE=256 in byterun/hash.c therefore specifying larger than 256 is equivalent with 256. This should be noted in the comment.
The text was updated successfully, but these errors were encountered: