I need to pack a large set of short strings into a single co...

Prompt

I need to pack a large set of short strings into a single contiguous blob to minimize the total memory footprint, then reference each original string by pointing into that blob with an offset and length. The blob is constructed once ahead of time, after which we only work with the packed representation and the pointers. The goal is to make the total memory used (the blob plus the pointer slice) as small as possible - ideally below the combined length of all input strings. You can exploit any structure you find: identical strings, strings that are substrings of others, overlapping suffixes/prefixes, etc. Do whatever it takes to shrink the blob. The returned strings do not need to be safe to mutate or outlive the blob - you may use unsafe.String to return them as views directly into the packed blob. Scale: there will be up to ~81 million strings, totaling over 1.7 GB of raw string data. Each individual string is at most 255 bytes. Constraints: - Construction must complete within a hard 10-minute runtime limit on a single machine. Construction time is not the primary metric, but you must finish within that window. - You get one attempt. Submit the best implementation you are capable of - optimize for the smallest footprint while staying correct and within the time limit. Implement your solution like this: ```go package string_packer type Pointer struct { Offset uint32 Length uint8 // strings are never >255 bytes } type StringMap struct {} func NewStringMap(entries []string) (*StringMap, []Pointer, error) { // the returned pointer slice must contain one Pointer per entry, // in the same order, each resolving back to the original string } // Get returns the original string (using unsafe.String) for a given pointer. func (s *StringMap) Get(p Pointer) (string, error) {} // Size returns the total size in bytes of the packed string blob. func (s *StringMap) Size() int {} ``` Deliver a single Go file containing only your implementation - no tests, no benchmarks, no commentary. You may add additional helper functions, methods, or fields as needed, but keep the public structure above intact.