Changgyoo Park
Changgyoo Park
Hi all, Thanks a lot for this incredible test framework. My colleagues and I use `loom` on a daily basis at work, and it has proved to be extremely useful...
@tomtomjhj Thanks for the tip, we'll use a `SeqCst fence` instead when it's needed once your branch gets merged into the main branch. _Send my regards to @jeehoonkang as my...
Implementing `Clone` is not as simple as it seems. It's true that the data structures are full of `ebr::Arc` for reference counting, but the unit of memory allocation is not...
`Clone` will be much faster under any circumstances than copy-on-iteration, however its semantics should be precisely defined for each struct first.
A rudimentary version of `Clone` is now implemented for container types: 0.8.2. Will be optimized in 0.8.3.
Will look into it in a few weeks (still, not optimized as of 0.10.2).
It is possible to bypass some locking and atomic operations while cloning a container type instance, but the expected gain is small (~99% cache hit ~= near-zero atomic operation penalty)....
This totally makes sense to me, since different modules/projects sharing the same data types are actually very common. Adding support for `use ::path::Name` is most preferable, but using an alias...
@loyd yes, correct.
`Ctrl + [` is the de facto standard `esc` alternative on macOS, and I don't think the usage is niche, because `Ctrl + [` is especially useful when your keyboard...