val_deleplace

6 ms·

1.
by val_deleplace 2y ago
We agreed to make the threadsafeness more explicit in the documentation of the 'unique' package: https://github.com/golang/go/issues/69637
2.
by val_deleplace 2y ago
I tested with many concurrent goroutines, and confirmed that calling `unique.Make` does not cause any data race condition
3.
by val_deleplace 2y ago
Yes, the package is designed to be thread-safe
4.
by val_deleplace 5y ago
Mere quadratic time complexity is something I would expect to timeout and catch at fuzzing time, as long as we do encourage non-tiny inputs, say 10K and beyond.
5.
by val_deleplace 5y ago
Yes, definitely dozens of pretty good online resources. Here are 3: - Tour of Go: https://tour.golang.org/ - Practical Go: Real world advice for writing maintainable Go programs, by Dave Cheney: https://dave.chen
6.
by val_deleplace 5y ago
You may upvote the Swift request here: https://github.com/Deleplace/programming-idioms/issues/30
7.
by val_deleplace 5y ago
Yep! Curation is though.
8.
by val_deleplace 5y ago
It's already possible and encouraged to improve the solutions. The "edit" button shows up on computer browsers, not on mobile if the screen is small. There's no "debate" capabilities, though.
9.
by val_deleplace 5y ago
Indeed! I updated the implementation to hoist the quadratic strlen.
10.
by val_deleplace 6y ago
I agree with the 2 example tasks, which are not "simple" to write. The remove-by-value snippet is 8 lines, and it can be wrong in a subtle way: if list contains pointers, then we have a memory leak beyond the slice final length (p
11.
by val_deleplace 6y ago
Author here: there were 2 initial use cases for me, (1) I'm familiar with the language X but I forget e.g. how to "check if a file exists" (2) I'm learning a new language Y, I know that "checking if a file exists&qu
12.
by val_deleplace 6y ago
You can vote for Swift here https://github.com/Deleplace/programming-idioms/issues/30
13.
by val_deleplace 6y ago
See https://github.com/divan/txqr for this use case. Other probably exist. It can be useful sometimes to not bother with any network at all, e.g. an international museum machine streaming map and documentation for tour
14.
by val_deleplace 7y ago
This submission being popular in HN caused an interesting traffic spike in Programming Idioms. Here is a detailed recital of the technical and financial consequences: https://medium.com/google-cloud/surviving-traffic-sp
15.
by val_deleplace 7y ago
This draft: https://github.com/dgryski/go-perfbook/blob/master/TODO This short list: https://github.com/enocom/gopher-reading-list#performance This article: https://medi
16.
by val_deleplace 8y ago
Hi iainmerrick, just for info the measured per-file cost didn't include reading from the filesystem. Only the in-memory parsing was taken into account.
17.
by val_deleplace 8y ago
scott_s you're totally right on both points. FWIW I really mean the "take the numbers with a grain of salt" advice, i.e. "Your mileage may vary". What I'm sharing in this article is not a bunch of hard, strong,
18.
by val_deleplace 8y ago
Hi jerf, please note that - the benchmark was designed to repeatedly parse an in-memory byte slice (not the hard drive), thus IO contention is unlikely here ; - concurrency is a big win when IO is a bottleneck : keep processing dozens of th