-
Sounds like they are aware that weak references will have some use (even internally), but it looks like if they accept such a thing, it will be a long ways off.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
In a somewhat related rant, I've spent an embarrassingly stupid amount of time writing out the referenced picker package (+ a couple of support packages) to basically serialize/deserialize elasticsearch types with minor validation. Despite a relatively obscene amount of code written for a trivial task (granted, Elastic's json is obnoxious but still...), I've barely scratched the surface with thin test coverage of around ~40%.
-
I too felt the same when I have to import binary_heap_plus crate which has comparators and worse is that these standards are not at all helpful for a developer. Ex: https://github.com/rust-lang/rust/issues/82001#issuecomment-778692012, they are not ready to merge becoz of performance characteristics of remove & contains function, WTF? Seriously as a BinaryHeap user I know the performance of these functions which touches O(N), as a Library provider they need to provide them, as a user I know where & when to use them. If there are performance penalties I know exactly WTF I am doing.