Feature: Add WrapAsThreadSafe

[mai7star]

Overview

• Added WrapAsThreadSafe() function
  • Upgrades threadUnsafeSet to threadSafeSet
  • Intended for use cases where initial data is populated under concurrent processing, then used as read-only afterward

Example

set := NewThreadUnsafeSet[int]()

// Add items to safeSet under concurrent processing (thread-safe here)
safeSet = WrapAsThreadSafe(set) 
safeSet.Append(i1, i2, i3...)

// Read operations on the original set
set.Contains(1)

[deckarep]

Just how useful is this for others out there? I'm not opposed to it but I'm also not sure that I want to go down this path.

It's not the kind of thing you blindly want to mix and match.

Example: doing operations with a threadsafe Set and a non-threadsafe are not compatible.