Closed achille-roussel closed 1 year ago
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
Thank you for the PR
Problem
I'm interested in getting ristretto to build to the new
wasip1
target, but it fails due to ristretto's assumption that the program is being compiled to a unix system where files can be mapped to memory. At this time, thex/sys/unix
package does not considerwasip1
to be a unix platform, and memory mapping isn't supported either when compiling to WebAssembly.Solution
The proposed solution in this PR is to provide stubs implementations of the memory mapping functions which return
ENOSYS
to indicate that the functionalities are not available when compiled toGOOS=wasip1
.If I'm reading the code correctly, this means that persisting data structures to a storage medium will not be supported, but the rest of ristretto should work as expected.
I believe this to be a useful trade-off since many dependents of ristretto only use the in-memory data structures (e.g. https://github.com/DataDog/datadog-agent/blob/main/pkg/obfuscate/cache.go, which is what I'm interested in getting to compile).
A more advanced solution could be to rework the
z.Buffer
internals so the data structure can work on platforms where mapping files to memory isn't supported; however, this represents a bigger undertaking, I would like to first unblock dependencies by allowing the program to compile.Please let me know if you have any concerns or feedback on the change!