Perhaps you should try some spelling variations:
"coder coder complexity recursive proof" » "coder coder complexity reduction proof" (Expand search), "coder coder complexity receivers proof" (Expand search), "coder coder complexity sensitive proof" (Expand search), "coder code complexity recursive proof" (Expand search), "coder model complexity recursive proof" (Expand search), "coder lower complexity recursive proof" (Expand search), "coder coder complexity discursive proof" (Expand search), "coder coder complexity decisive proof" (Expand search), "coder coder complexity recursive process" (Expand search), "coder decoder complexity recursive proof" (Expand search), "code code complexity recursive proof" (Expand search), "decoder codec complexity recursive proof" (Expand search)
"in python python python programming" » "in pythons python python programming" (Expand search), "in piton python python programming" (Expand search), "in pitons python python programming" (Expand search), "_ python python python programming" (Expand search)

You may be able to get more results by adjusting your search query.

• Performing a fuzzy search may retrieve terms with similar spellings: (("coder coder complexity recursive proof") OR ("in python python python programming"))~.
• The words AND, OR and NOT may confuse the search; try adding quotes: "((\"coder coder complexity recursive proof\") OR (\"in python python python programming\"))".
• Removing quotes may allow a broader search: (( coder coder complexity recursive proof ) OR ( in python python python programming )).
• Adding a wildcard symbol may retrieve word variants: (("coder coder complexity recursive proof") OR ("in python python python programming"))*.