The documentation gives some hints that the default hashtable and hashset implementation are assuming C strings as keys. However, the "official" documentation use some defines that have been removed in the meantime, i.e. in 9b4c3cb. As of now using the hashing data structures with anything but strings as keys is rather a PITA. There is al

We should have mutation tests running in the Eclipse Collections build so we can discover and address more edge cases in our tests.

Pitest

The link to "Table of Contents" points to a forked version. It should point to the official repo in the jupyterlab org.

I expected Validated to have an ap method or something, but I can't seem to find it. The only docs I can see are https://github.com/aol/cyclops/wiki/Validator, which clearly isn't the current implementation, and I notice aol/cyclops#826 as another issue, but I don't see the proposed ap method.

I have noticed that when calling Collection.update with { multi: true } set as an option, the collection.before.update hook is called once per document, however, the modifier parameter is the same object that was used in the previous iteration.

This is dangerous if we are setting modifier values based solely on the individual properties of the document we are currently iterating over.

I'm trying to find out how to fit vue-mc into my app's architecture, and the docs are helpful, but maybe I am missing something obvious:

In the Vue docs data section, it reads:

A rule of thumb is that data should just be data - it is not recommended to observe objects with their own stateful behavior.

Where should I store my model instance otherwise?

I'm looking for some clarification about the intended behavior for toArray(). As per the current project documentation, the toArray() method (emphasis mine):

Converts the collection to array recursively.

A recursive operation implies that a collection of collections would be converted into an array of arrays; however, the current behavior just calls iterator_to_array on the to

There is some immediate backlash about immutable collections by Java users, as their understanding of the concept is either getting a full copy per operation, or receiving an exception on mutating methods.

The persistent keyword along with some references to Big O perf in the documentation may help spread the understanding of the difference.