CthulhuDen

I did a bit of testnig and it turns our the first case is likely handled by phpstorm itself (as evidenced by the fact I still get autocomplete and arguments...

Thanks for your reply. Sadly, I cannot see this setting anywhere  Thanks for the plugin anyway, it's great help for php projects!

But isn't it the case that the keys are usually non-fixed-length? My use case involves storing (small number of) different strings and finding/inserting (if new) them frequently (like 1 mil...

Now imagine if `Trie` wasn't parameterized (I'm new to rust so not sure on exact signature) ``` struct Trie(Vec); impl Trie { fn insert(&mut self, key: &K) where Vec: Borrow,...

I could pass reference (instantiate `K` to reference type), but I would have to fix lifetime of references which I can pass to `insert`/`entry` for each `Trie` instance, which is...

Ok so maybe example: ``` let mut trie: Trie = Trie::new(); { let keyFromSomewhere = [a, b, c]; trie.entry(&keyFromSomewhere[..]); } { let keyFromSomewhereElse = [d, e, f]; trie.entry(&keyFromSomewhereElse[..]); } ```...

Thanks for having a look at the issue. However considering I want to avoid copying the keys because of high intensity of requests, I dont think leaking the keys memory...

Hey! So it does seem like the issue got a little stale, do you think I could offer my take on this?

@farnz Please go ahead! Sorry I don't have numbers on hand to back me, but I found this fix changes nothing, cause we're always bottlenecked on either input or output...