Constructive Separations and Their Consequences
Abstract
For a complexity class and language , a constructive separation of gives an efficient algorithm (also called a refuter) to find counterexamples (bad inputs) for every -algorithm attempting to decide . We study the questions: Which lower bounds can be made constructive? What are the consequences of constructive separations? We build a case that "constructiveness" serves as a dividing line between many weak lower bounds we know how to prove, and strong lower bounds against , , and . Put another way, constructiveness is the opposite of a complexity barrier: it is a property we want lower bounds to have. Our results fall into three broad categories. 1. Our first set of results shows that, for many well-known lower bounds against streaming algorithms, one-tape Turing machines, and query complexity, as well as lower bounds for the Minimum Circuit Size Problem, making these lower bounds constructive would imply breakthrough separations ranging from to even . 2. Our second set of results shows that for most major open problems in lower bounds against , , and , including , , , , and , any proof of the separation would further imply a constructive separation. Our results generalize earlier results for [Gutfreund, Shaltiel, and Ta-Shma, CCC 2005] and [Dolev, Fandina and Gutfreund, CIAC 2013]. 3. Our third set of results shows that certain complexity separations cannot be made constructive. We observe that for all super-polynomially growing functions , there are no constructive separations for detecting high -time Kolmogorov complexity (a task which is known to be not in ) from any complexity class, unconditionally.
Cite
@article{arxiv.2203.14379,
title = {Constructive Separations and Their Consequences},
author = {Lijie Chen and Ce Jin and Rahul Santhanam and Ryan Williams},
journal= {arXiv preprint arXiv:2203.14379},
year = {2024}
}
Comments
Abstract shortened to fit arXiv requirements