So I was using Opus exclusively (Max plan) to write Rust since June. CC switched to Sonnet 4.5 by default yesterday, I'm just very unimpressed. It seems like a

So I was using Opus exclusively (Max plan) to write Rust since June. CC switched to Sonnet 4.5 by default yesterday, I'm just very unimpressed. It seems like a considerable regression. Probably this is related to me using it to write Rust and not Python or JS/TS? Example: I asked it to refactor a for loop to functional code with rayon, compiler barfs about mutation (it used par_iter()). It rolls back the code to what it was before. Then this happens: Me: There is par_iter_mut(). Sonnet: Ah yes, but we can't use par_iter_mut() on self.vertices because we're calling self.set_vertex_position() which needs mutable access to the entire mesh (not just the vertices map). However, self is &mut. Wtf? This would have never happened with Opus, i.e. Opus would have used par_iter_mut() to start with (or applied the right fix w/o hand-holding after the compile failed with par_iter()). I had just a bunch of those wtfs since yesterday from more or less zero before. I.e. it doesn't feel like coincidence.