refactor LookupKey logic to reduce redundancy
          #1635
        
          
      
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Change Summary
Precursor to #1620, which is itself a precursor to moving forward with pydantic/jiter#184
The idea here is that the
LookupPathstuff contains a bunch of redundantStringandPy<PyString>values. I work these away.I also removed
Cloneimplementation at the same time, which gets us closer to removing PyO3'spy-clonefeature.Related issue number
N/A
Checklist
pydantic-core(except for expected changes)