Skip to content

Commit 123770e

Browse files
committed
Update README
1 parent d4b8399 commit 123770e

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
[![Actions Status](https://github.com/chillenzer/KitGenBench/workflows/Install/badge.svg)](https://github.com/chillenzer/KitGenBench/actions)
33
[![codecov](https://codecov.io/gh/chillenzer/KitGenBench/branch/master/graph/badge.svg)](https://codecov.io/gh/chillenzer/KitGenBench)
44

5-
Have you ever sat in a restaurant and wondered: Why the heck do they already have their Cock Au Vin on the next table and my simple pasta is taking forever? If you're anything like us, you immediately apply for funding to set up a large scale experiment measuring preparation times for all combinations of recipes. It's, of course, the only reasonable thing to do.
5+
*Have you ever sat in a restaurant and wondered: Why the heck do they already have their Cock Au Vin on the next table and my simple pasta is taking forever? If you're anything like us, you immediately apply for funding to set up a large scale experiment measuring preparation times for all combinations of recipes. It's, of course, the only reasonable thing to do.*
66

7-
Well, we can't help you with the funding. What we can offer you is a comfy kitchen bench to take a seat, observe and come up with a unified theory of bolognesio synthesis revolutionising the field. So, compose your recipe, lean back and observe...
7+
*Well, we can't help you with the funding. What we can offer you is a comfy kitchen bench to take a seat, observe and come up with a unified theory of bolognesio synthesis revolutionising the field. So, compose your recipe, lean back and observe...*
88

9-
Wait, did we say "kitchen bench"? We meant...
9+
*Wait, did we say "kitchen bench"? We meant...*
1010

1111
# KitGenBench
1212

@@ -25,6 +25,7 @@ These are:
2525
- a logger saying how to record what happens during the benchmark
2626

2727
The main loop of the program is as simple as (up to technical details)
28+
2829
```C++
2930
while (not recipeExhausted) {
3031
result = logger.call([]{recipe.next();});

0 commit comments

Comments
 (0)