You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/introduction.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -364,21 +364,17 @@ The library supports four graph topologies:
364
364
-**UnitDiskGraph** — geometric graph where edges connect vertices within a distance threshold (for quantum hardware mapping)
365
365
-**HyperGraph** — generalized edges connecting any number of vertices
366
366
367
-
## Quick Example
367
+
## Our vision
368
368
369
-
```rust
370
-
useproblemreductions::prelude::*;
369
+
In the past, computational complexity theorists focus mostly on the theory part, left the tedious implementation to developers. This `algorithm -> paper` mode causes many repeated efforts in algorithm implementation. Due to the lack of infrastructures, many fundamental issues can not be answered clearly, such as
370
+
- What is the fastest algorithm for solving a problem?
371
+
- Given an efficient solver, what are the potential high impact problems it can be used for?
371
372
372
-
// Create an Independent Set problem on a triangle graph
Imagine, if every problem in this world is connected as a directed reduction graph, such that given any pairs of problems, we can easily find the most efficient reduction path between them. We can create a high speed rail-way between any two problems. We will no longer have repeated efforts in solving problems that are essentially the "same". However, developing this software infrastructure is not easy.
374
374
375
-
// Solve with brute force
376
-
letsolver=BruteForce::new();
377
-
letsolutions=solver.find_best(&problem);
375
+
What if AI take over the implementation part, and complete the `algoirthm -> paper -> software` pipeline? Theorists can still focus on the theory part, and AI will do the heavy lifting. How is it possible? Can we trust AI's implementation? Our answer is, yes. Not only due to the fast evolving large language models brings new power, but also due to the fact that almost all reductions can be verified by running round-trip tests (`source -> target -> solution to target -> solution to source` must equal to `source -> solution to source`). We can easily verify the correctness of the reduction by checking round-trip reduction examples.
378
376
379
-
// Maximum independent set in a triangle has size 1
Our vision is to automate this test-driven development pipeline, and enable general public to contribute. Our software will be open sourced, forever, for at any physical location in the universe to every human being and AI agent.
0 commit comments