Comment author: @lefessan

A new function Hashtbl.reset has been added to resize the bucket table to its initial size.

Comment author: @rixed

It's not quite resizing. So the user is supposed to track the size of the hash and reset it when judged appropriate ?

Comment author: @lefessan

True, it's not resizing, it is clearing and resetting to the initial size. Users should only use it if they need to recover some space, otherwise, they probably want to keep the current size and just clear all entries.

Comment author: @rixed

Oh, reading your comment then the actual diff I realize that reset also clears the hashtbl.

I then respectfully disagree with closing this ticket, then.
That's very nice to have both clear and reset behavior (but I'd favor to add an optional boolean argument to clear that would additionnally shrinks the hash size).

It seams to me that the initial concern was that when using long lived hashtables which sizes may vary in great proportion then the overall size of all hashtable growth continuously, which hurts memory and thus performances.

I understand that shrinking dynamically a hash is a tedious topic (one must avoid to continuously grow/shrink), though.

Comment author: Christoph Bauer

I would have expect, that Hashtbl.remove calls resize like add, if the table is less than 3/8 (or 1/4) full.