Vince Broz

This is mainly something I find helpful in prompting me to go back and add more comprehensive tests for changes. We can [formally make it optional](https://stackoverflow.com/questions/78072432/how-to-enable-a-single-github-action-to-not-block-a-merge) or just rely on...

Superceded by #996

I'm not terribly familiar with Arch Linux - any chance you could provide a recipe to reproduce this in Docker? Suspect that something is lying to us about the gem...

Sounds good. Regardless, I think we should add an exception handler and move onto the next gem, as Linux distributions definitely do move gems around when installed by system packages....

This will be a bit of a change in user experience - folks will see e.g. `Array(Integer, String)` instead of just `Array` on `foo = [1, "bar"]`. I haven't experienced...

@castwide: In your case, would the types be varied? If not, I think I taught Chain::Array to create Array instead of Array(X, X, X, X) or what have you for...

That makes sense to me. I've been running with it for three weeks now and have been pretty happy with it, but I think we have options if folks want...

This was spit out during a recent run of the specs: ``` # terminated with exception (report_on_exception is true): /Users/broz/.rbenv/versions/3.1.6/lib/ruby/gems/3.1.0/gems/rubocop-1.74.0/lib/rubocop/config_loader.rb:80:in `chdir': conflicting chdir during another chdir block (RuntimeError) from /Users/broz/.rbenv/versions/3.1.6/lib/ruby/gems/3.1.0/gems/rubocop-1.74.0/lib/rubocop/config_loader.rb:80:in...

Should be fixed by https://github.com/castwide/solargraph/pull/1007, which adds a lock around known directory changes

I was also working to understand the motivation for that feature - if it's something that should stick around, it'd be great leave a breadcrumb for the next person. Maybe...